New domain and old certificate: Q for Rich?

[Snarpy]

My client wants to change his domain name. We added the new domain as an IRM, but get a security warning (of couse, why didn't I think of this) when using the new domain. Is it available to transfer the certificate to a new domain, since the rest of the info hasn't changed? Does the domain have to be the main domain, or can it be an IRM?

Snarpy

[hobbes]

If the cert is in the IRM's name, then you can change the IRM to a full package and have the cert used for it. Otherwise, you cannot have the domain on the cert changed once it's issued; you will need to get a new cert.

[Rich]

Hobbes is correct that a new domain name requires a new certificate--the Certifying Authorities issue certs on a per-domain basis.

FutureQuest will need to answer whether an IRM can have certificate assigned to it, but I think the answer is that only the main domain can have a cert assigned to it.

The bottom line is that there is no such thing as a "domain name change" since you cannot go anywher and actually "change" a domain name. You can get a new domain name but the old one still exists.

[Melissa]

FutureQuest will need to answer whether an IRM can have certificate assigned to it, but I think the answer is that only the main domain can have a cert assigned to it.Figure that's my cue... ;)

SSL can only be set up on the Full Package (not IRs):
http://service.FutureQuest.net/index.php?_a=knowledgebase&_j=questiondetails&_i=247

[Snarpy]

That's what I thought, and warned the client about, but it never hurts to ask. Thanks Melissa and Rich (and Hobbes). Now I'll give him the bad news. :sprint:

Snarpy