Q and A

Question:

I'm using an older Lotus Notes Driver (prior to v3.5) on my Domino 6 system, and when a new Lotus Notes person is created in the Notes Address Book with the same FirstName LastName, the Notes driver rejects the add command with a "user already exists" error. Why is this happening, and how can I avoid this?

Answer:

The Lotus Notes registration process checks the new user's FullName field for duplicates within the Notes Address Book. If a match is found, then the registration process performs a user merge and takes the new user information and writes it on top of the existing Lotus Notes user in the NAB. This is typically an undesirable event for IDM and the NotesDriverShim as the end result will have two Identity Vault objects associated with one Lotus Notes user. Therefore, by default, the NotesDriverShim also checks for duplicates prior to user registration (processing a user add command). If the FullName already exists, then the user add command is rejected with a 'user already exists' error by the NotesDriverShim. Using the NotesDriverShim v3.5, you can disable this Notes User FullName check for uniqueness that is performed by the NotesDriverShim by using the custom parameter 'registration-dest-dn-check="false"' as an attribute on the Add command element. See the Driver for Lotus Notes Implementation Guide documentation for more details on the registration-dest-dn-check custom parameter.

Here is an old cool solution tip that shows one method of creating Notes users with unique FullName fields: http://www.novell.com/coolsolutions/tip/17694.html

The above tip provides a solution that uses an XSLT style sheet. IDM 3.5 provides improved DirXML Script capabilities that allow this style sheet to be ported/implemented in DirXML Script quite easily.