--On Tuesday, November 3, 2020 6:51 PM +0000 paul.jc@yahoo.com wrote:
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:
Hi Peter,
You would need to search your back-mdb database and see if there are any objects with an objectClass of "alias". I.e.,
ldapsearch ... "(objectClass=alias") 1.1
filling in your bind details of course (I'd suggest something with full read access to the entire db).
Regards, Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com