From e908e97338f180dd406f192a2e1154379b943256 Mon Sep 17 00:00:00 2001 From: Gavin Henry Date: Thu, 6 Sep 2007 22:08:24 +0000 Subject: [PATCH] authzFrom removed. --- doc/guide/admin/overlays.sdf | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/doc/guide/admin/overlays.sdf b/doc/guide/admin/overlays.sdf index 40b8b3f46e..88b1ef53dc 100644 --- a/doc/guide/admin/overlays.sdf +++ b/doc/guide/admin/overlays.sdf @@ -111,16 +111,13 @@ definitions: > credentials="" > mode="self" > chain-tls start -> chain-idassert-authzFrom "*" > chain-return-error TRUE > updateref "ldap://ldapmaster.example.com/" The {{B:chain-tls}} statement enables TLS from the slave to the ldap master. -The {{B:chain-idassert-authzFrom}} statement will assert the identity of whatever -bound dn on the slave is making the update request. The DITs are exactly the -same between these machines, therefore whatever user bound to the slave will -also exist on the master. If that DN does not have update privileges on the master, -nothing will happen. +The DITs are exactly the same between these machines, therefore whatever user +bound to the slave will also exist on the master. If that DN does not have +update privileges on the master, nothing will happen. You will need to restart the slave after these changes. Then, if you are using {{loglevel 256}}, you can monitor an {{ldapmodify}} on the slave and the master. -- 2.39.5