Subject: Changelog format of LDAP ModifyRDN
Author: eLDAP
In response to: Line Command of LDAP ModiyRDN
Posted on: 12/08/2006 01:56:54 PM
In some case a changelog is required for replication purpose. Here is the format sepcified in SPEC: draft-good-ldap-changelog-04.txt
changeNumber: the change number, as assigned by the supplier. This
integer MUST strictly increase as new entries are added, and must
always be unique within a given server.
Syntax: INTEGER
targetdn: the distinguished name of the entry which was added,
modified or deleted. In the case of a modrdn operation, the
targetdn gives the DN of the entry before it was modified.
Syntax: DN
changeType: the type of change. One of: "add", "delete", "modify",
"modrdn". Later RFCs may define additional values for changeType.
Syntax: DirectoryString
changes: the changes which were made to the directory server. These
changes are in LDIF format, which is described in [1].
Syntax: OctetString
newRDN: the new RDN (Relative Distinguished Name) of the entry, if
the changeType is "modrdn". If the changeType attribute does not
have the value "modrdn", then there should be no values contained in
the newRDN attribute.
Syntax: DN
deleteOldRDN: a flag which tells whether the old RDN of the entry
should be retained as a distinguished attribute of the entry, or
should be deleted. A value of "FALSE" indicates that the RDN should
be retained as a distinguished attribute, and a value of "TRUE"
indicates that it should not be retained as a distinguished
attribute of the entry. If any value other than "TRUE" or "FALSE"
is contained in the deleteOldRDN, the RDN should be retained as a
distinguished attribute (that is, "FALSE" is the default if no
values are present, or if illegal values are present).
Syntax: BOOLEAN
newSuperior: if present, gives the name of the entry which becomes
the immediate superior of the existing entry. This optional
attribute reflects LDAPv3 functionality, and MUST NOT be generated
by LDAPv2 servers [2].
Syntax: DN
Example:
A changeLogEntry representing a modrdn operation
performed on an entry in the directory
dn: changenumber=10042, cn=changelog
changenumber: 10042
targetdn: cn=Bjorn Jensen, ou=Product Development, o=Ace Industry,
c=US
changetype: modrdn
newrdn: cn=Bjorn J Jensen
deleteoldrdn: FALSE
>
> On 12/04/2006 08:39:32 PM
eLDAP wrote:
The above testing runs can also be done by SunOne Directory line command ldapmodify.exe in conjunction with the corresponding LDIF (RFC 2849):
# Modify an entry's relative distinguished name
dn: cn=Paul Jensen, ou=Product Development, dc=airius, dc=com
changetype: modrdn
newrdn: cn=Paula Jensen
deleteoldrdn: 1
# Rename an entry and move all of its children to a new location in
# the directory tree (only implemented by LDAPv3 servers).
dn: ou=PD Accountants, ou=Product Development, dc=airius, dc=com
changetype: modrdn
newrdn: ou=Product Development Accountants
deleteoldrdn: 0
newsuperior: ou=Accounting, dc=airius, dc=com
References:
