https://bugs.openldap.org/show_bug.cgi?id=9281

Issue ID: 9281 Summary: attribute "aliasedObjectName" not supported in context when using postgres Product: OpenLDAP Version: 2.4.50 Hardware: All OS: Linux Status: UNCONFIRMED Severity: normal Priority: --- Component: backends Assignee: bugs@openldap.org Reporter: thomas.fazekas@gmail.com Target Milestone: ---

I've found a number of posts mentioning that the SQL backend does not support "alias" class, but all those posts were dated before 2004 so I just suspect that by now this feature is suppose to be developed which means either I'm making a mistake during configuration or I stumbled upon a bug.

Basically I try to use the following ldif to create an alias :

# link1, httpd users, debbie.topfer.com dn: cn=link1,ou=httpd users,o=mytest,dc=com objectClass: alias objectClass: extensibleObject aliasedObjectName: cn=testuser1,ou=accounts,o=mytest,dc=com cn: link1

obviously the target exists (cn=testuser1,ou=accounts,o=mytest,dc=com)

Now this work with the mdb backend but if I use sql I get the following error :

5ef4ff0e backsql_add("cn=link1,ou=httpd users,o=mytest,dc=com"): entry failed schema check -- aborting 5ef4ff0e send_ldap_result: conn=1000 op=1 p=3 5ef4ff0e send_ldap_result: err=65 matched="" text="attribute "aliasedObjectName" not supported in context"

What am I missing ? Is there any other log that I should submit to get this sorted ?