SSL Certificates and WebAccess

[Marvin Huffaker]

I've noticed that in a lot of networks that use GroupWise and WebAccess, the actual server name is different than the DNS name used to connect to the server via the Internet. For example, the server might be called SERVER1.COMPANY.COM internally, but to the outside it is called MAIL.COMPANY.COM.

When setting up SSL certificates, this creates unwanted browser verification because the SSL Certificate name that is generated is always the actual name of the server as it resides in the tree.

My question is this, is there a way to generate a certificate so that the name matches the MAIL.COMPANY.COM that people will actually be using to access it from the outside? Thus preventing the "Server Name Mismatch" error in Internet Explorer when the site is accessed?

Thanks.

Marvin Huffaker, MCNE
Marvin Huffaker Consulting
Novell NetWare Solutions & Support
www.redjuju.com • 480-988-7215

[Joseph Moore [SysOp]]

Marvin Huffaker:

> My question is this, is there a way to generate a certificate so that the name matches the MAIL.COMPANY.COM that people will actually be using to access it from the outside?
>

certainly - http://support.novell.com/cgi-bin/search/searchtid.cgi?/10072424.htm

Joe Moore
Novell Support Connection Volunteer Sysop
http://just.fdisk-it.com - Coming soon:
"Migrating From NetWare Enterprise Web Server to Apache 1.3.x"
for an e-book on NetWare Enterprise Web Server,
see http://www.caledonia.net/sysops.html

NO EMAIL PLEASE!!!!!