[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: problem with aliases
At 01:20 PM 4/1/2003, Marek Turczyniak wrote:
>openldap 2.1.16, bdb 4.1 (both compiled), redhat 7.2
Back-bdb provides no alias support.
Back-ldbm provides incomplete (and experimental) alias support. YMMV.
>My problem is that I can't add alias. My ldif looks like:
>
>dn: uid=virt-112, ou=People, dc=nowy, dc=pl
>objectclass: alias
>aliasedObjectName: uid=virt-112,ou=virtuals,dc=nowy,dc=pl
>
>and ldapadd says:
>ldap_add: No such attribute (16)
> additional info: naming attribute 'uid' is not present in entry
You can only name entries using values it contains.
>if I add to ldif file
> uid: virt-112
>
>ldapadd says:
>ldap_add: Object class violation (65)
> additional info: attribute 'uid' not allowed
The 'alias' class doesn't allow 'uid'. You need to augment
the objectClass with another class which allows 'uid', such
as uidObject or extensibleObject.
>This problem appears also with bdb4, ldbm (gdbm 1.0.8) but it works on my
>another host with openldap 2.0.11-13, and ldbm (gdbm 1.8.0-10) (both from
>redhat packages).
2.0 is more lax than 2.1.