From: Howard Chu <hyc@openldap.org>
Date: Sat, 20 Apr 2002 07:44:02 +0000 (+0000)
Subject: DN consistency, lowercase, etc.
X-Git-Tag: OPENLDAP_REL_ENG_2_MP~159
X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=e94d18e501828ce6a42fd73b6b4d35eec19b1ffc;p=openldap

DN consistency, lowercase, etc.
---

diff --git a/doc/guide/admin/sasl.sdf b/doc/guide/admin/sasl.sdf
index 2dfb4380d2..c309263156 100644
--- a/doc/guide/admin/sasl.sdf
+++ b/doc/guide/admin/sasl.sdf
@@ -265,11 +265,11 @@ pattern, the variables $2, $3, etc are used.
 For example, suppose the user's authentication identity is written
 as the DN string
 
->	uid=ADAMSON,cn=EXAMPLE.COM,cn=KERBEROS_V4,cn=AUTH
+>	uid=adamson,cn=example.com,cn=kerberos_v4,cn=auth
 
 and the user's actual LDAP entry is
 
->	uid=ADAMSON,ou=PERSON,dc=EXAMPLE,dc=COM
+>	uid=adamson,ou=person,dc=example,dc=com
 
 The {{EX:saslRegexp}} directive in {{slapd.conf}}(5) could be
 written
@@ -451,7 +451,7 @@ Authorization identities of this form are converted into a DN format
 by the same function that the authentication process used, producing
 an {{authorization request DN}} of the form
 
->	uid=<username>,cn=<realm>,cn=auth
+>	uid=<username>,cn=<realm>,cn=<mechanism>,cn=auth
 
 That authorization request DN is then run through the same
 {{EX:saslRegexp}} process to convert it into a legitimate authorization