lekkimworld.comldap

Active Directory error messages - useful for LDAP access

Fri, 26 Jun 2009 12:15:47 GMT

Found this nice summary of the error messages Active Directory can return when trying to connect using LDAP (e.g. from Java using JNDI).

Active Directory LDAP Errors

Apache Directory Studio

Fri, 23 Nov 2007 17:06:22 GMT

I'm currently on a Lotus Connections project and needed a LDAP browser to test authentication and searching. Previously I have been using a Java LDAP browser with a UI that really was lacking. Today I discovered Apache Directory Studio which is built on the Eclipse platform. The application is free and a really good LDAP browser. It also contains a LDIF editor.

The application is a full fletched LDAP browser and is made up of a couple of Eclipse features. You can download the application as a standalone RCP (rich client platform) application, as features for your existing Eclipse IDE but should actually just as well be able to use the LDAP browser directly from Notes 8 Standard. The LDAP browser ships with a perspective so it should be doable.

If it ran inside of Notes 8 it would be a killer admin. tool and easily distributable inside your organization.

I tried to install the perspective in Notes 8 but it isn't possible since the features depend on the org.eclipse.search feature which isn't shipped with Notes 8. org.eclipse.search is however supplied with the standard Eclipse 3.2.1 which is the same version as Expeditor 6.1.1 builds upon so it should be possible to download the Directory Studio source code and repackage the perspective to do a perspective which is installable in Notes 8.

For now however I have to run the application in Eclipse or as standalone.

Demystifying LDAP

Tue, 01 Aug 2006 04:50:43 GMT

Demystifying LDAP via dzone.com...

Change to LDAP Directory Assistance (in Domino 7)

Mon, 19 Jun 2006 18:51:38 GMT

Or at least I think the change was in Domino 7... I never noticed it before since we have been using a custom DSAPI authentication module to work around the shortcoming in previous Domino releases.

The change is that the @Username function now returns the distinguished name of the authenticated user separated with slashes (/) even though it is a LDAP name and hence really separated by commas. This is �ber nice since it means we can scrap the custom DSAPI module and move the application from a Domino 5.x server to a Domino 7 server (we are having big issues deploying the DSAPI filter on Domino 7).

Sweet!

(For the record - my custom DSAPI filter does more than convert LDAP names separated by commas to names separated by slashes. It also handles dynamic LDAP groups composed on the groupOfUrls objectClass. If you need something like that let me know.)