Powerful Directory Management Tool

[smithdu]

It appears the 2.6 browser negotiates SSL even if the SSL cert presented by the LDAP server contains an invalid CN.

Steps to recreate:
1. Configure a profile in the browser to connect to serverA.domain.com
2. Put an SSL cert on serverA with CN=ServerB.domain.com in the subject field.
3. Connect with 2.6 browser and it does not even give a warning.

SSL is used for server auth and encryption. It appears the 2.6 browser is somehow ignoring the server auth part. I realize the next version is supposed to use the MS API and this may not get much interest. I just would like to know if I am missing something.

[Support]

Probably some problems exist, but, unfortunately, LDAP Browser development is frozen, so chances are really low that the issue would be fixed any time soon.