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

Re: slurpd error: creatorsName: no user modification allowed

At 01:51 PM 10/13/2004, Andreas wrote:
>On Wed, Oct 13, 2004 at 05:40:03PM -0300, Bruno Negrão wrote:
>> The "replica" directive needs a "credential" parameter to set the binddn's 
>> password slurpd goona use. But in the slave machine, the "updatedn" 
>> directive doesn't specify a corresponding "credential" parameter.
>> How can I set in the slave machine what is the password of the updatedn 
>> (when this is not the same as the rootdn)?
>The updatedn is just a binddn as any other one. So, either you have some SASL
>mechanism to authenticate this dn or you have an entry in the directory for
>this binddn and an userPassword attribute in it. You don't specify a password
>for it in the configuration file as may be done with rootdn.

Note that documentation is attempting to discourage one
from configuring the updatedn to be the MASTER's rootdn.
It's fine for the updatedn to be SLAVE's rootdn (as long
as this differs from the MASTER's rootdn).  I often use
something like "cn=Manager,dc=example,dc=com" as the
Master's rootdn, something like "cn=Replica,dc=example,dc=com"
as the Slave's rootdn and updatedn.  This works just fine.