|
A standard SSL key will only work for the
FQDN you supply as the common name. If it’s www.abc.com,
then that’s ALL that will work. If it’s
secure.abc.com or cheeseburger.abc.com, whatever it is, you are restricted to
just that. Few notes here though… Usually it’s customary to get www.abc.com and do a redirect from abc.com to www.abc.com on entry to the site, so you don’t
have to worry about people that don’t use the www. The SSL key will actually apply encryption
for ANY domain you use it on, it will just offer an error the first time someone
tries it at a FQDN that doesn’t match exactly what is in the key. This
warning error is usually a bad thing. There are wildcard ssl keys which would
handle [anything].abc.com or [anything].RandD.abc.com. They cost about the same
as 4 standard keys, so if you have 5+ variants you want to protect, they make
sense. Witango also sees a difference between www.abc.com and secure.abc.com. It’s
important to note that if you pass a user from www.abc.com
to secure.abc.com you could loose variables, notably in the domain space. To
compensate for this, you should setup domains.ini appropriately. Check out www.geotrust.com, I’ve been happy
with them for about 2.5 years now, and they cost a little less than Verisign
with great service. Robert -----Original Message----- Sorry, quick clarification please. If the domain is
“abc.com” and I want to use a secure certificate for
“secure.abc.com”, which one is considered the fully qualified
domain name (common name)? If I register “abc.com” will the
certificate work for “secure.abc.com”,
“private.abc.com”, etc. Thanks, Chuck Lockwood ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf |
- Witango-Talk: OT: Secure certificates Chuck Lockwood
- RE: Witango-Talk: OT: Secure certificates Ian Daniel
- RE: Witango-Talk: OT: Secure certificates Troy Sosamon
- Re: Witango-Talk: OT: Secure certificates Robert Shubert
- Re: Witango-Talk: OT: Secure certificates roberts
