From 62107d5dd7203a6edbc5b484c97b1da07c629cc6 Mon Sep 17 00:00:00 2001 From: Howard Chu Date: Thu, 13 Jan 2005 18:58:58 +0000 Subject: [PATCH] Delete syncrepl updatedn --- doc/guide/admin/syncrepl.sdf | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/doc/guide/admin/syncrepl.sdf b/doc/guide/admin/syncrepl.sdf index cb8252d8f5..c21895bc4b 100644 --- a/doc/guide/admin/syncrepl.sdf +++ b/doc/guide/admin/syncrepl.sdf @@ -356,7 +356,6 @@ can be defined with any database type. > scope=sub > attrs="cn,sn,ou,telephoneNumber,title,l" > schemachecking=off -> updatedn="cn=replica,dc=example,dc=com" > bindmethod=simple > binddn="cn=syncuser,dc=example,dc=com" > credentials=secret @@ -368,10 +367,8 @@ bind as {{EX:cn=syncuser,dc=example,dc=com}} using simple authentication with password "secret". Note that the access control privilege of {{EX:cn=syncuser,dc=example,dc=com}} should be set appropriately in the provider to retrieve the desired replication content. -The consumer will write to its database with the privilege of the -{{EX:cn=replica,dc=example,dc=com}} entry as specified in the -{{EX:updatedn=}} directive. The {{EX:updatedn}} entry should have -write permission to the replica content. +The consumer uses the rootdn to write to its database so it +always has full permissions to write all content. The synchronization search in the above example will search for the entries whose objectClass is organizationalPerson in the entire subtree -- 2.39.5