Re: [389-users] using uid rather then cn in the binddn

[Dumbo Q]

Thanks.  I tried that, but now it tells me
ldapmodify: Object class violation (65)
        additional info: missing attribute "cn" required by object class
"inetOrgPerson"

Being that the entry has a 'cn', I guess this means that somewhere I have it setup
where dn requires the cn to be in it ???  Anythoughts





________________________________
From: Nathan Kinder <nkinder(a)redhat.com&gt;
To: General discussion list for the 389 Directory server project.
<fedora-directory-users(a)redhat.com&gt;
Sent: Monday, June 22, 2009 4:30:53 PM
Subject: Re: [389-users] using uid rather then cn in the binddn

Dumbo Q wrote:
>  Erg.    I thought I had it but it's something is blocking me from
> doing this update. Can anyone help me find where my constraint is?
>   
<snip>
>  
>  [root@rhds ~]# ldapmodify -x -W -D cn=DirectoryManager
>  dn: cn=testy,ou=users,ou=people,dc=mydomain,dc=com
>  changetype: modify
>  newRDN: uid=testy
>  deleteOldRDN: 1
>  
>  modifying entry "cn=testy,ou=users,ou=people,dc=mydomain,dc=com"
>  ldapmodify: Object class violation (65)
>          additional info: attribute "newRdn" not allowed 
You need to
perform a "modrdn" operation instead of a regular modify.  Try the above, but
change your "changetype" to "modrdn".  You may also find that you
don't want to delete the old RDN from the entry, particularly if that is the only
"cn" value present in your entry.  Doing so would cause an objectclass violation
since "cn" is likely required for the objectclass you are using.
>  
>  
>  
>  ------------------------------------------------------------------------
>  
>  --
>  389 users mailing list
>  389-users(a)redhat.com
>  https://www.redhat.com/mailman/listinfo/fedora-directory-users
>    
--
389 users mailing list
389-users(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-directory-users