Closed
Bug 5608
Opened 26 years ago
Closed 26 years ago
modifyRDN only changes CN value from the DN
Categories
(Directory :: PerLDAP, defect, P3)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: si, Assigned: leif)
Details
Using modifyRDN to change the OU value of an DN entry, returns
"LDAP error: Protocol error".
Using the rename.pl example provided with the library, the error
is the same.
Having an LDAP entry with the following DN value:
dn: cn=frf, ou=est SI, o=UPCNET, c=ES
If I call rename.pl with: (connection parameters not supplied)
./rename.pl (...) "cn=frf" "cn=frf, ou=est FIB, o=UPCNET, c=ES"
I get the following error:
"LDAP error: Protocol error"
The only way it works, is if I do the following:
./rename.pl (...) "cn=frf" "cn=anotherValue"
and the resulting DN value in the ldap database is:
dn: cn=anotherValue, ou=est SI, o=UPCNET, c=ES
How could I change the OU value from the DN ?
(I'm using perldap v.1.2.2)
Assignee | ||
Updated•26 years ago
|
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → INVALID
Assignee | ||
Comment 1•26 years ago
|
||
This is not a bug. The Netscape (and OpenLDAP) server can only do modify RDN,
meaning you can not change the second (or other) DN components. The only DN
component that can be changed like this is the RDN, or the naming attribute.
Sorry, nothing I can do about this, it's a limitation in the server. The only
way to do it is to search for the old entry (get all attributes), delete the
entry, modify the DN as you like, and then recreate the new entry.
-- Leif
You need to log in
before you can comment on or make changes to this bug.
Description
•