Quanah Gibson-Mount wrote:
If you're using aliases in your LDAP DB, then yes, that'll absolutely trigger issues such as this. The use of aliases generally indicates poor DIT design. ;)
Hey Quanah, understood. :) I inherited this openldap database and I'm not well versed in aliases. How do I verify if I actually have aliases being utilized? I have no ldif files in my core or custom schema config that define aliases. An ldapsearch on the cn=config returns default references, but that is all:
olcAttributeTypes: ( 2.5.4.1 NAME ( 'aliasedObjectName' 'aliasedEntryName' ) D ESC 'RFC4512: name of aliased object' EQUALITY distinguishedNameMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 SINGLE-VALUE )
and
olcObjectClasses: ( 2.5.6.1 NAME 'alias' DESC 'RFC4512: an alias' SUP top STRU CTURAL MUST aliasedObjectName )
Is there something else I should search to verify usage of aliases in the DB?
Thanks. Paul