LDAP SSL and Subject Alternate Names

It seems that when using SAN names with the domain controller certificate, only the first name is of importance, all other names are being ignored?
LVL 3
albatros99Asked:
Who is Participating?
 
SreRajConnect With a Mentor Commented:
Hi,

Yes, it looks like this is a requirement. Please see the following text from a MS Article.
--------------------------------
Enabling LDAPS for domain controllers using a multi-tier CA hierarchy

•The Subject name or the first name in the Subject Alternative Name (SAN) must match the Fully Qualified Domain Name (FQDN) of the host machine, such as Subject:CN=server1.contoso.com.
--------------------------------

http://social.technet.microsoft.com/wiki/contents/articles/2980.ldap-over-ssl-ldaps-certificate.aspx
0
 
Tony MassaCommented:
http://support.microsoft.com/kb/931351

You can use an additional SAN, but the first SAN attribute name MUST match the FQDN of the server.  If you wanted to use LDAPS.US.YOURDOMAIN.COM for multiple servers to provide round-robin load balancing of LDAPS, for example, you would use the SAN attribute as:

SAN:server1.yourdomain.com&ldaps.us.yourdomain.com
SAN:server2.yourdomain.com&ldaps.us.yourdomain.com
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.