Jarek Gawor's excellent LDAP Browser/Editor v2.8.2

2 Likes
over 12 years ago
Jarek Gawor's excellent LDAP Browser/Editor v2.8.2 - though last updated in 2001, still one of the best! Works perfectly with current java version 5 and 6.

All previous download links seem to be broken, so here's a refresh for all who prefer superfast and minimalistic tools like me.

Here's the readme:

LDAP Browser/Editor 2.8.2 Release Notes, April 25th, 2001

The LDAP Browser/Editor 2.8.2 is a maintenance release. It contains a number of bug fixes and various improvements described below. It also contains a couple of new features. For a complete list of changes see the changes.txt file included with the distribution.

New Features/Improvements:

1. Multiple windows: Multiple windows/connections can be opened at the same time without starting a separate JVM for each connection.
2. Improved UTF8 support for various functions and operations.
3. For authenticated connections, the password does not need to be stored in the configuration file anymore. The Browser will prompt the user for the password when needed.
4. Improved configuration. Generic and static Browser settings are now pulled and stored in a separate configuration file. See What is lbe.properties file? question for details.
5. PKCS12 support: The CA certificates, and client certificates can now be loaded from the PKCS12 files. The files must have .p12 extension to be loaded in the PKCS12 format. This functionality relies on the JSSE and its support for PKCS12 standard.
6. Partial internationalization: This is an initial effort to internationalize the entire code and translate it into a couple of languages. Right now only a small portion of the code is internationalized and only Polish translation is provided.

Bug Fixes:

1. Backslash characters ('\') were not properly escaped in the session files.
2. UTF8 encoded distinguished names were incorrectly encoded/decoded in ldap urls.

Current limitations/bugs:

* LDIF changetypes are not supported.
* No schema integration.
* No VLV/Paged results support.
* Fetch DN only works with ldap v3 servers.
* Various window refresh problems - due to bugs in JVM.

Other Notes:

If running the Browser with JVM 1.3 you might encounter some problems with the JNDI library. JVM 1.3 includes an older version of the JNDI library then the version that is distributed with the Browser. 1.3 will load the older version instead of the Browser version. To force the Browser to load its version of the JNDI library using the 'lbe' script pass 'fix13' as the first parameter to the script. Examples: on Windows type: lbe.bat fix13 on Unix/Linux type: lbe.sh fix13.

Mac OS X:

The Browser was successfully tested on Mac OS X.

Labels:

How To-Best Practice
Collateral
Comment List
Anonymous
Parents
  • Alas there is at least one bad bug in this tool, specific to eDirectory that has two affects.

    If you edit an object and add an attribute, it may re-write the values in sasLoginConfigurationKey (actually all the sasLoginConfiguration* attributes) which contain the challenge/response questions, Secret Store data, and Simple Password. This WILL corrupt them.

    This will manifest with strange errors trying to use any of this encrypted data. I forget the error code we saw in User App, but I think it might have been a 618 DS error on the attributes when you try to read or set the Challenge Response questions.

    It also looks like the DirXML-EntitlementRef if present will experience a similar process, in that it will rewrite them, and thus fire your Entitlements processing rules., which is not as bad as the corruption, but annoying.
Comment
  • Alas there is at least one bad bug in this tool, specific to eDirectory that has two affects.

    If you edit an object and add an attribute, it may re-write the values in sasLoginConfigurationKey (actually all the sasLoginConfiguration* attributes) which contain the challenge/response questions, Secret Store data, and Simple Password. This WILL corrupt them.

    This will manifest with strange errors trying to use any of this encrypted data. I forget the error code we saw in User App, but I think it might have been a 618 DS error on the attributes when you try to read or set the Challenge Response questions.

    It also looks like the DirXML-EntitlementRef if present will experience a similar process, in that it will rewrite them, and thus fire your Entitlements processing rules., which is not as bad as the corruption, but annoying.
Children
No Data
Related Discussions
Recommended