Remove custom domain verification process
I'm running a blogging service and need to allow customers to point their own custom domains to my GAE app. I know that I can link a domain to my Google account and then use that domain to serve app engine, but this process does not scale and requires that I have direct access to the customer's domain register/DNS. The only other alternative is to force my customers to sign up for Google Apps (why!).
Almost all other PaaS make this process painless:
- In Heroku, I simply add the domain to a whitelist and the customer adds a CNAME record.
- In AWS, it's even easier: customers would only need to add a CNAME record pointing to the instance.
I think the problem here is that GCP is arbitrarily linked to the "Webmaster Central" service which we don't need or care about.
This isn't a niche use-case and would apply to anyone building web services involving third-party owned domains.
We love GCP and want to keep out business here. Please lift this arbitrary and infuriating limitation!
Fili Wiese commented
FYI: You can utilize the site verification API (https://developers.google.com/site-verification/v1/getting_started), potentially in combination with https://cloud.google.com/dns and verify user domains. Just be mindful there are limits on how many domains you verify per account.
I am running into the same issues. Did you find a way to get around this? Or did you simply switch to one of the other services... considering my question is already a couple of years behind i hope there is a solution..
Hatsekee! Support commented
I am having the same problems. Requiring my customers to verify their domain for App Engine is far to inconvenient and time consuming. So much even, that it is preventing me from migrating all of our infra over to GCP.
A whitelist - like Heroku - along with a CNAME would be a far better implementation for me.
Another solution might be verification trough provisioning an HTTP resource, like uploading a file to the root path of the (sub)domain.