A LDAP issue that many can learn from
Tags :LDAP
Imagine if you will......
a Domino environment running for
some time under R4 into R5. They aggregated a while ago into the
Domino Directory for LDAP (as well they should right?) and all was well.
They were point to attributes, pulling information, authenticating.
Then the upgrade to Domino 6. Some
authentication and lookups stop functioning. The schema database
was recreated properly. Some applications still work great. Yet
some lookups are failing now from some other systems. Binding works
fine and all use the same account to bind. What oh what could it
be?
| Problem |
| In Domino R5, the LDAP attribute
Shortname was set by default. It mapped to the field "Shortname"
in the Person document. However, in Domino 6.x this attribute does
not exist.
|
| Content |
| Both Shortname and UID map to
the field "Shortname". In Domino 6.x, the attribute Shortname
was removed as this was redundant.
It is possible, however, to add the attribute with the following steps: 1. In the Domino Directory create a Configuration document set to be used as the default settings for all servers (on the Basics tab). 2. On the LDAP tab, in edit mode, click the "Select Attribute Types" button. 3. In the drop-down box "Object Classes" select dominoPerson. 4. Click "New", type Shortname in the New Field window and click OK. 5. Click OK for the LDAP Attribute Type Selection window. 6. Save the Configuration document and restart your server. Supporting Information: NOTE: The above information applies only to anonymous searches; this does not actually add the attribute back for LDAP. The document titled "LDAP Queries On "Shortname" Fail To Return Results" (#1160538) describes how to put the shortname back in the schema, and so would then work for authenticated searches. Both steps must be performed for authenticated and anonymous searches. |
blog comments powered by Disqus
On Thursday, June 2nd, 2005 by Chris Miller
