Deprecation - Version 1
The first version of SSL for SaaS will be deprecated on September 1, 2021.
In SSL for SaaS v1, traffic for Custom Hostnames is proxied to the origin based on the IP addresses assigned to the zone with SSL for SaaS enabled. This IP-based routing introduces complexities that prevented customers from making changes with zero downtime.
SSL for SaaS v2 removes IP-based routing and its associated problems. Instead, traffic is proxied to the origin based on the custom hostname of the SaaS zone. This means that Custom Hostnames will now need to pass a hostname verification step after Custom Hostname creation and in addition to SSL certificate validation. This adds a layer of security from SSL for SaaS v1 by ensuring that only verified hostnames are proxied to your origin.
To ensure that your service is not disrupted, you need to perform an additional ownership check on every new Custom Hostname. There are three methods to verify ownership: TXT, HTTP, and CNAME. Use TXT and HTTP for pre-validation to validate the Custom Hostname before traffic is proxied by Cloudflare’s edge.
Using a TXT or HTTP validation method helps you avoid downtime during your migration. If you choose to use CNAME validation, your domain might fall behind on its backoff schedule.
When creating a Custom Hostname with the TXT method through the API, a TXT ownership_verification record is provided for your customer to add to their DNS for the ownership validation check. When the TXT record is added, the Custom Hostname will be marked as Active in the Cloudflare SSL/TLS app under the Custom Hostnames tab.
When creating a Custom Hostname with the HTTP through the API, an HTTP ownership_verification token is provided. HTTP verification is used mainly by organizations with a large deployed base of custom domains with HTTPS support. Serving the HTTP token from your origin web server allows hostname verification before proxying domain traffic through Cloudflare.
Cloudflare sends GET requests to the http_url using User-Agent: Cloudflare Custom Hostname Verification.
If you validated a hostname that is not proxying traffic through Cloudflare, the Custom Hostname will be marked as Active in the Cloudflare SSL/TLS app when the HTTP token is verified (under the Custom Hostnames tab).
If your hostname is already proxying traffic through Cloudflare, then HTTP validation is not enough by itself and the hostname will only go active when DNS-based validation is complete.
Though you can use CNAME validation, we recommend you either use a TXT or HTTP validation method.
Custom Hostnames can also be validated once Cloudflare detects that the Custom Hostname is a CNAME record pointing to the fallback record configured for the SSL for SaaS domain. Though this is the simplest validation method, it increases the risk of errors. Since a CNAME record would also route traffic to Cloudflare’s edge, traffic may reach our edge before the Custom Hostname has completed validation or the SSL certificate has issued.
Once you have tested and added the hostname validation step to your Custom Hostname creation process, please contact your Cloudflare Account Team to schedule a date to migrate your SSL for SaaS v1 zones. Your Cloudflare Account Team will work with you to validate your existing Custom Hostnames without downtime.
Both BYOIP addresses and IP addresses configured for Apex Proxying allow for hostname validation to complete successfully by having either a BYOIP address or an Apex Proxy IP address as the target of a DNS A record for a custom hostname.
SSL for SaaS v2 is functionally equivalent to SSL for SaaS v1, but removes the requirements to use specific anycast IP addresses at Cloudflare’s edge and Cloudflare’s Universal SSL product with the SSL for SaaS zone.
Once the migration has been started for your zone(s), Cloudflare will require every Custom Hostname to pass a hostname verification check. Existing Custom Hostnames that are proxying to Cloudflare with a DNS CNAME record will automatically re-validate and migrate to the new version with no downtime. Any Custom Hostnames created after the start of the migration will need to pass the hostname validation check using one of the validation methods mentioned above.
Before your migration, you should:
- To test validation methods, set up a test zone and ask your Solutions Engineer (SE) to enable SSL for SaaS v2.
- Wait for your SE to run our pre-migration tool. This tool groups your hostnames into one of the following statuses:
test_pending: In the process of being verified or was unable to be verified and re-queued for verification. A custom hostname will be re-queued 25 times before moving to thetest_failedstatus.test_active: Passed CNAME verificationtest_active_apex: Passed Apex Proxy verificationtest_blocked: Hostname will be blocked during the migration because hostname belongs to a banned zone. Contact your CSM to verify banned custom hostnames and proceed with the migration.test_failed: Failed hostname verification 25 times
- Review the results of our pre-migration tool (run by your Solutions Engineer) using one of the following methods:
- Via the API:
https://api.cloudflare.com/client/v4/zones/{zone_tag}/custom_hostnames?hostname_status={status} - Via a CSV file (provided by your SE)
- Via the Cloudflare dashboard:
- Via the API:
- Approve the migration. Your Cloudflare account team will work with you to schedule a migration window for each of your SSL for SaaS zones.
After the migration has started and has had some time to progress, Cloudflare will generate a list of Custom Hostnames that failed to migrate and ask for your approval to complete the migration. When you give your approval, the migration will be complete, SSL for SaaS v1 will be disabled for the zone, and any Custom Hostname that has not completed hostname validation will no longer function.
The migration timeline depends on the number of Custom Hostnames. For example, if a zone has fewer than 10,000 Custom Hostnames, the list can be generated around an hour after beginning the migration. If a zone has millions of Custom Hostnames, it may take up to 24 hours to identify instances that failed to successfully migrate.
When your Cloudflare Account Team asks for approval to complete the migration, please respond in a timely manner. You will have two weeks to validate any remaining Custom Hostnames before they are systematically deleted.
The migration process starts on March 31, 2021 and will continue until final deprecation on September 1, 2021.
If you would like to begin the migration process before March 31, 2021, please contact your Cloudflare Account Team and they will work with you to expedite the process. Otherwise, your Cloudflare Account Team will reach out to you with a time for a migration window so that your zones are migrated before September 1, 2021 end-of-life date.
If you have any questions, please contact your Cloudflare Account Team or SaaSv2@cloudflare.com.