Topics

When you migrate a user from an LDIF file, if you select the option "Add full name provided to the Notes person document," the migration tool adds the user's LDAP distinguished name (DN) to the Notes Person document as a secondary user name. The primary user name is always derived from a user's First Name and Last Name components, together with the organizational information taken from the Certifier ID. This is true, even if the user is migrated as a directory entry only, and is not registered as a Notes user.

For example, if you used the /Acme Corp certifier ID to import the following LDIF file:

dn: cn=Bruce Bitter, ou=Product Development, o=Acme, c=US
objectclass: top
objectclass: person
objectclass: organizationalPerson
objectclass: inetOrgPerson
ou: Product Development
cn: Bruce Bitter
cn: BBitter
cn: BBitter Alias
sn: Bitter
givenname: Bruce
l: Boston
uid: bbitter
mail: bbitter@acme.com

After the migration completes, the following names appear in the User Name field of the Person document, regardless of whether you register the user:

Bruce Bitter/Acme Corp
Bruce Bitter
Bruce Bitter/Product Development/Acme/US
Bbitter
Bbitter Alias

Note that the organizational modifier for the primary name (/Acme Corp) is derived from the Certifier ID, not from any attribute in the LDIF file.

LDAP searches of the Domino Directory examine only the primary user names in the Person document. As a result, if you specify a search base to limit the search to the organizational hierarchy found in the imported DN (/Product Development/Acme/US), the search would fail, since the specified base does not exist in the Domino Directory. To correctly search the Domino Directory for this user, specify the search base "o=Acme Corp."

ldapsearch -l 300 -L -h server -b "o=Acme Corp" "(cn=Bruce Bitter*)"

If you are not sure of the correct base, do not specify a search base. When no base is specified, the search attempts to locate the user in all available hierarchies.