773815 - Get a signed SSL cert for developer-new.

Status: RESOLVED WONTFIX

(developer.mozilla.org Graveyard :: Wiki pages, defect, P1)

Description

[John Karahalis [:openjck]]

We are currently using a self-signed cert on developer-new, causing "Add an exception" warnings for Firefox users.

Assuming SSL certs are tied to machines and not domains (woefully ignorant -- correct me if I'm wrong), we will need to get a signed SSL cert for the server currently called developer-new. This will need to be done before the launch in July.

Comment 1

[David Walsh :davidwalsh]

Security certificates are tied to hostnames, so every subdomain requires a different SSL cert.  For example, "developer-new.mozilla.org" cannot use "developer.mozilla.org" or "mozilla.org" SSL certs. :/

Comment 2

[John Karahalis [:openjck]]

Good to know. So then when we update the developer.mozilla.org DNS to point to the new server, will our existing SSL cert work?

Comment 3

[Jean-Yves Perrier [:teoli]]

It will be valid, yes. (It already "works" but fail the validation as the hostname is different).

Comment 4

[Jake Maul [:jakem]]

Closing this out. As indicated above, certs are tied to domain names and not servers, so what'll happen is that when developer-new.mozilla.org becomes production and is renamed to developer.mozilla.org, it will "just work".