[Date Prev][Date Next] [Chronological] [Thread] [Top]

syncrepl mangles operational attributes (ITS#3259)



Full_Name: Greg Matthews
Version: 2.2.14
OS: Linux and Solaris
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (192.171.172.12)


When using syncrepl to replicate a database instance, the entryUUID attribute on
the consumer has a garbage value and some operational attributes are missing.
This can be demonstrated by simply starting a consumer instance with an empty
database and letting it grab its DIT from the provider. The entryUUID values
will be base64 encoded but when decoded they contain nothing recognisable.

Here is an example:
dn: dc=my-domain,dc=com
dc: my-domain
objectClass: top
objectClass: domain
structuralObjectClass: domain
entryCSN: 20040727135905Z#000001#00#000000
entryUUID:: 3ciq2HQgECiV+OnB6i4R7g==

the corresponding object on the provider is:
dn: dc=my-domain,dc=com
dc: my-domain
objectClass: top
objectClass: domain
structuralObjectClass: domain
entryUUID: ddc8aad8-7420-1028-95f8-e9c1ea2e11ee
creatorsName: cn=Manager,dc=my-domain,dc=com
modifiersName: cn=Manager,dc=my-domain,dc=com
createTimestamp: 20040727135905Z
modifyTimestamp: 20040727135905Z
entryCSN: 20040727135905Z#000001#00#000000

the config:
...
database bdb
suffix          "dc=my-domain,dc=com"
rootdn          "cn=Manager,dc=my-domain,dc=com"
rootpw          secret
directory       /usr/local/var/openldap-data
syncrepl rid=1
 provider=ldap://my.ldap.server
 updatedn="cn=manager,dc=my-domain,dc=com"
 binddn="cn=manager,dc=my-domain,dc=com"
 bindmethod=simple
 credentials=secret
 searchbase="dc=my-domain,dc=com"
 type=refreshonly
 interval=00:00:01:00

index   objectClass     eq