Security Certificate in IIS
For the Outlook Web Access, I've got 2 ways to access it. They are internal access (https://mailgate/....) and external access (https://webmail/....).
However, I will get the certificate warning either Internal or External access.
the cause is the certicate name is different from the FQDN in the URL. Problem if we use certificate named "webmail.XXX.XX.XX" it will work for external access but if accessing internally it displays the warning because they are using "mailgate" for URL. Same happens vice-versa. And we can only use 1 certficate per site in IIS as fas as I'm aware.
Basically i want to suppress the certificate warning for internal and external access. The IE6 warning did not look dangerous, and i could even disable it. So it's only become a problem with the installation of IE7. And also recent Firefox versions.
I'm lookin for a solution at server level because I cant enforce browser settings outside the network.
And suggestions and idea???
Software/Hardware used:
Software/Hardware used:
ASKED:
July 22, 2008 12:56 AM
UPDATED:
July 23, 2008 11:52 AM
Answer Wiki:
We had the same problem. I just asked the Certificate Authority to add a "Subject Alternative Name" that matches the internal name to a single certificate. This is through verisign. not sure if other CA will do the same.
example:
email.company.net - Subject Name
another.company.net - Subject Alternative Name
===================
Take a look at my <a href="http://itknowledgeexchange.techtarget.com/it-trenches/certificates-who-do-you-trust/">blog entry</a> about certificates and Exchange. This will help you understand why this is happening. The clients need to have a path to or trust the root certificate authority.
To see all answers submitted to the Answer Wiki: View Answer History.
RSS - Discussions Help
Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
