[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
updateref not working
- To: openldap-software@OpenLDAP.org
- Subject: updateref not working
- From: "Sean Hussey" <seanhussey@gmail.com>
- Date: Wed, 1 Mar 2006 13:06:25 -0500
- Content-disposition: inline
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=iSSaDj2/2NZ9yRFFoFNjNmKQXFKhMg3WtJasWQpOUXGL7bN4yshSt8Do1oN42btVhO2OyksVM3Pow+y9ifRt4ClJO0kOrXMmvYuFoHrkEq9vMjS88Z9RYhcg1v3LxsRkpRzkjtqMpJ8UvWd/HZRWyUWwhBq11BUepsalp1Chxr4=
Hi everyone,
We're on OpenLDAP 2.2.29, but we've had this problem since 2.2.17 (or
so). Our master is configured to replicate to the slaves via slurpd.
That works.
What doesn't work is having the slaves update the master when a change
comes through. As far as I know, these are the configurations we
need:
Slave servers:
updatedn "uid=replica,dc=host,dc=com"
updateref ldap://ldapmaster.host.com
Master server:
replica uri=ldap://ldapchild1.host.com:389
suffix="dc=host,dc=com"
binddn="uid=replica,dc=host,dc=com"
credentials=secret
bindmethod=simple
tls=yes
uid=replica is the rootdn of the slaves. On the slaves, rootpw is an
MD5 hash. On the master, the credentials are plaintext. Could that
be the issue?
Thanks,
Sean