How do we verify domains if using G Suite (Google Apps)

[Kipland Iles]

We use Atlassian Cloud and we have users from two separate domains (both using G Suite). We don't host our website for one domain but we do for the other. We do have control over the domain records, though. Have you considered providing TXT record verification (similar to Amazon SES)?

Our public websites are also not running SSL so no HTTPS there. For us to use HTML verification we would have to setup subdomains just for this purpose. Issue again is that only one domain uses a wildcard SSL cert. The other is static for one URL (www.OURDOMAIN.COM).

I'm not clear on how to proceed. HTML validation might be problematic.

[EsperantoXL]

I've the same problem our site is not https site.

Why not a txt record verification in the DNS like Google?

[Alessandro Grena]

I've a very similar problem, our site is in HTTP only, and i tried by enabling HTTPS with a non-valid certificate but still cannot verify the domain in Atlassian. This is quite annoying.

Can someone from Atlassian figure out how we can verify our domains without having to enable HTTPS with a valid cert?

[Daniel Eads]

Hi all,

Just following up on this thread with links to the feature requests for this on jira.atlassian.com:

Confluence: CONFCLOUD-58334

Jira: JRACLOUD-68281

Voting on these issues will help our product managers prioritize the impact against other features being requested. And watching the tickets will let you follow along when development work happens!

Cheers,
Daniel

[Mark Maleitzke]

I totally agree. Why has no one from Atlassian responded to this? Is there at least an issue open on it we can vote on?

[Kipland Iles]

I verify domains at GoDaddy for SSL certs using either DNS TXT record verification (if I manage the domain) or HTTP verification (if I don't have access to the the DNS records). I also use DNS TXT record verification to verify domains for Amazon SES. Even using HTTP verification I can simply place a HTML file at the root of the web server that is hosting the domain being verified. There is no requirement for SSL on those domains since this relies on the fact that I have access to the web server.

We authenticate to Confluence/JIRA using our email addresses (no Google integration) and I would assume most others do, as well. I would think that not everyone authenticating would also have a public website running SSL that matches their email domain. Even if they do, most would redirect their "naked" domain to WWW.

I would prefer that we have the option for DNS TXT record verification since that is quick and easy for most folks. If HTML verification is the only way then I would suggest that Atlassian allow either HTTP or HTTPS and also allow a www prefix but HTML verification will not work for everyone. DNS TXT record verification should work for everyone but might be more difficult for those not managing their own domain record sets. I think we need both options but remove the requirement for SSL on HTML verification and allow a naked domain redirect.

[James Sullivan]

I have a similar problem. We currently host our site on Squarespace... and they do not support uploading files to the root directory like that.

[Mark Maleitzke]

I'm having a similar problem. If we want to verify the domain that gets used in email (mydomain.com), then verifying www.mydomain.com doesn't accomplish getting the base domain validated.

The problem with mydomain.com (without www prefix) is that our DNS is handled by a DNS provider. The DNS provider does redirects from the base domain to the www domain, but they don't do HTTPS. It's understandable that DNS vendors aren't going to support HTTPS for base domain redirects because that would involve the DNS provider having to install a certificate issued to us onto their redirect server (that services hundreds of clients).

I think Atlassian will find this is a quite common situation with many companies.

When validating a base domain, we ought to have the option to verify it by using the www equivalent; I believe that's how the certificate providers do their domain verification. - OR - If Atlassian wants to stick with hitting the base domain, they ought to provide the option for the file to be served over http.

Until this gets fixed in one way or another, we're stuck and can't get our domains validated.