From: Kurt Zeilenga <kurt@openldap.org>
Date: Fri, 6 Oct 2000 21:19:20 +0000 (+0000)
Subject: Comment on rootpw only be valid if rootdn is with namingContext
X-Git-Tag: LDBM_PRE_GIANT_RWLOCK~1801
X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=1e7fe604e9e59edc03d2216655c9fbc7b5ee27cc;p=openldap

Comment on rootpw only be valid if rootdn is with namingContext
---

diff --git a/doc/man/man5/slapd.conf.5 b/doc/man/man5/slapd.conf.5
index 039356364f..85ce15abcc 100644
--- a/doc/man/man5/slapd.conf.5
+++ b/doc/man/man5/slapd.conf.5
@@ -554,10 +554,16 @@ or administrative limit restrictions for operations on this database.
 This DN may or may not be associated with an entry.  An empty root
 DN (the default) specifies no root access is to be granted.  It is
 recommended that the rootdn only be specified when needed (such as
-when initially populating a database).
+when initially populating a database).  If the rootdn is within
+a namingContext (suffix) of the database, a simple bind password
+may also be provided using the
+.B rootpw
+directive.
 .TP
 .B rootpw <password>
-Specify a password (or hash of the password) for the rootdn.
+Specify a password (or hash of the password) for the rootdn.  If
+the rootdn is not within the namingContext of the database, the
+provided password is ignored.
 This option accepts all RFC 2307 userPassword formats known to
 the server (see 
 .B password-hash