Softerra Ldap Browser

I'm was attempting to evaluate LDAP Browser 2.6. I have LDAP Administrator 3.0 on the same machine. I am connecting to a remote iPlanet LDAP using SSL.

In this example, we use the names ldap-client.crt and ldap-client.key. In the Softerra LDAP Browser, install the key pair. Go to Tools Certificate Manager. Click Import Click Next. Click Browse In the File type drop-down list in the lower-right corner of the dialog box, select Personal Information Exchange (.pfx;.p12).

4.5

I would like to introduce a third-party LDAP admin tool here - the softerra ldap browser tool. It usually used to investigate the LDAP issue by L3 engineers. Now we will focus on how to gather the specified user's information and provide the output to IBM for review. Softerra LDAP Browser is a lightweight version of Softerra LDAP Administrator with limited functionality and is absolutely FREE for all kinds of use including commercial. Unlike Softerra LDAP Administrator, the Browser does not allow its users to modify LDAP directories. It is a perfect solution for people wishing to learn the LDAP technology but unsure they can handle all the complexity of. Softerra LDAP Browser is the industry-leading software for browsing and analyzing LDAP directories. It provides a wide variety of features for handy viewing of directory contents, getting.


Softerra ldap browser 4.5I have created an identical profile to that in the Administrator product with SSL enabled, but the Browser always reports a code 81. I am using the same login and therefore the same certificates etc which I have confirmed are working as I can connect using LDAP Administrator residing on the same server and connecting to the same LDAP.

Softerra Ldap Browser Manual


Softerra Ldap Browser 4.5

LDAP browser claims to support SSL, but when clicking the 'Try to use secure connection' in the server properties, the URL on the General tap still displays ldap://xxx:636 instead of ldaps://xxx:636 and it is the same for the window title. Therefore I'm not sure if is actually trying to create an SSL connection at all, or whether these are just display bugs?