I'm trying to migrate like for like an existing Sun Directory instance across to eDir, they have a IDM Interface that points to Sun IDM that I am going to replace like for like with Novell IDM 4.5 Standard. But I have run into an odd issue on the named by "uid" in the ldap namespace, which then maps to "uniqueID" in the eDir namespace. When I create a new user it always has CN as it's naming attribute not "uniqueID" even though I specify it in the qualified-dest-dn
I can query my record I created via a LDIF file I imported via ICE using IDM:
ab;270001 Wrote: > I think you can set an XML property of 'naming="true"' on the attribute > of > your choice to indicate that it should be the naming attribute; see an > example here: > > http://tinyurl.com/zfkyyuu
Tried with naming=true in the add-attr and going back to the non-qualified dest-dn, and it doesn't work the naming for the record is back to CN.
peter lambrechtsen <email@example.com> wrote: > ab;270001 Wrote: > I think you can set an XML property of 'naming="true"' on the attribute > of >> your choice to indicate that it should be the naming attribute; see an >> example here: >> >> http://tinyurl.com/zfkyyuu > > Tried with naming=true in the add-attr and going back to the non-qualified dest-dn, and it doesn't work the naming for the record is back to CN. > > <add class-name="User" dest-dn="internet\people\plambrechtsen"> > <add-attr attr-name="uniqueID" naming="true"> > <value>plambrechtsen</value> > </add-attr> > > So the dest-dn as a fully qualified value is the way to do it.
I recall I had this issue many years back and came to same conclusion as you.
-- If you find this post helpful and are logged into the web interface, show your appreciation and click on the star below...