Hi
jchambers,
I totally agree with you that requiring users to install an old piece of software just to handle a CA certificate is pretty lame. There is however a way to get SSL working in LDAP Browser 2.x without having to install Netscape. Here's how
o Importing the CA certificate on the Softerra Browser LDAP client software
After you have extracted the public key certificate of the Certificate Authority (CA) of the Active Directory server, you must import it into a cert7.db file that Softerra LDAP Browser can handle. There, Softerra's documentation says that you're supposed to install Netscape 4.x but you don't. You can simply use Mozilla's NSS utilities, and the certutil command line utility to do just the same.
However, the latest version of NSS does not generate a .db that is compatible with the older version that Softerra uses (cert7.db vs. cert8.db) and there does not appear to be flag in certutil to generate a .db with the old compatibility mode. Therefore you have to use an older version of NSS. The most recent version that does that is (apparently) NSS 3.3.2, which you can download, precompiled for win32 platforms, from
ftp://ftp.mozilla.org/pub/mozilla.org/security/nss/releases/NSS_3_3_2_RTM/WINNT4.0_OPT.OBJ
Once you've extracted the zip and placed your certificate (eg: myserver_ca.cer) in the bin directory, you should run the following commands:
- Code: Select all
C:\nss-3.3.2\bin>certutil -N -d .
(this generates the key3.db and cert7.db that Softerra requires)
and
- Code: Select all
C:\nss-3.3.2\bin>certutil -A -n "root_ca" -t "C,," -a -i .\myserver_ca.cer -d .
o Configuring the Softerra LDAP profile for LDAPS
1. Overwrite the key3.db and cert7.db files from the LDAP Browser root directory with the ones just created
2. Edit your existing LDAP profile and change the port to the secure one (eg. 636)
3. on the "LDAP Settings" tab, check the box "Try to use secure connection (only LDAP v.3)"
That did the trick for me when using an Active Directory controller with LDAPS (which was setup following the documentation from IBM
here).
Hope this will be useful to others.