alias and extensibleObject

[Rowan Rodrik <bigsmoke@home.nl>]

Hi all,

I used to add aliases by combining them with a simple auxiliary object class
called name object with only a cn attribute. I didn't like this because I
didn't want to needlessly extend the standard schema.

Now I read that  I could use the extensibleObject auxiliary object class
to add _any_ attribute to an entry, so I tried the following:

ldapadd -D "cn=Manager,o=BigSmoke,c=NL" -x -w l33tp4ssw0rd
dn: cn=Popko Peter van der Molen,ou=Friends,ou=Contacts,o=BigSmoke,c=NL
objectClass: top
objectClass: alias
objectClass: extensibleObject
aliasedObjectName: cn=Popko Peter van der Molen,ou=van der 
Molen,ou=Family,ou=Contacts,o=BigSmoke,c=NL
cn: Popko Peter van der Molen

adding new entry "cn=Popko Peter van der 
Molen,ou=Friends,ou=Contacts,o=BigSmoke,c=NL"
ldapadd: update failed: cn=Popko Peter van der 
Molen,ou=Friends,ou=Contacts,o=BigSmoke,c=NL
ldap_add: Object class violation (65)
        additional info: attribute "aliasedObjectName" not supported in 
context

Could anyone hint me at why this doesn't work?

Thanks for your time,

  - Rowan Rodrik

PS: I almost sent this message to openldap-dev because it only became clear to
me which mailing list to send this question to after reading the
confirmation message of openldap-dev. It might be a good idea to
add something to the OpenLDAP Software charter along the lines of:
This includes the discussion on development of OpenLDAP enabled
applications that use the OpenLDAP SDK.

And maybe add something to the openldap-dev charter like:
Discussion about the development of OpenLDAP _enabled_ applications
should go to openldap-software; this list only discusses software that
is _part of_ OpenLDAP.

But, it might as well be due to my raging stupidity that I didn't catch this
right away.

PPS: It might also be a good idea to make the list charters section the first
section, even before "Subscribing to a List".

-- 
Life is like a chocolate: to taste it, you must take it from its box.