diff --git a/samples/ldap/src/main/webapp/WEB-INF/applicationContext-security.xml b/samples/ldap/src/main/webapp/WEB-INF/applicationContext-security.xml
index 6b314fcd69..ae398e5e74 100644
--- a/samples/ldap/src/main/webapp/WEB-INF/applicationContext-security.xml
+++ b/samples/ldap/src/main/webapp/WEB-INF/applicationContext-security.xml
@@ -1,32 +1,65 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
\ No newline at end of file
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/src/docbkx/ldap-auth-provider.xml b/src/docbkx/ldap-auth-provider.xml
index 1d64aa6302..748cacf4eb 100644
--- a/src/docbkx/ldap-auth-provider.xml
+++ b/src/docbkx/ldap-auth-provider.xml
@@ -239,7 +239,7 @@
is used, and the login name will be substituted for the parameter
{0}. The pattern should be relative to the DN that the
configured
- InitialDirContextFactory
+ SpringSecurityContextSource
will bind to (see the section on
connecting to the LDAP server
for more information on this). For example, if you are using an LDAP server with
@@ -323,6 +323,17 @@
which will be replaced with the user's login name.
+
+ LdapAuthoritiesPopulator
+
+ After authenticating the user successfully, the LdapAuthenticationProvider
+ will attempt to load a set of authorities for the user by calling the configured
+ LdapAuthoritiesPopulator bean. The DefaultLdapAuthoritiesPopulator
+ is an implementation which will load the authorities by searching the directory for groups of which the user is a member
+ (typically these will be groupOfNames or groupOfUniqueNames entries in the directory).
+ Consult the Javadoc for this class for more details on how it works.
+
+ Spring Bean Configuration
@@ -367,7 +378,7 @@
(member=<user's-DN>). The role name will be taken from the
ou
attribute of each match.
- To configurae a user search object, which uses the filter
+ To configure a user search object, which uses the filter
(uid=<user-login-name>)
for use instead of the DN-pattern (or in addition to it), you would configure the
following bean
@@ -403,7 +414,7 @@ public interface UserDetailsContextMapper {
void mapUserToContext(UserDetails user, DirContextAdapter ctx);
}]]>
- Only the first method is relevant for authentication. If you provide an implememntation of this, you can
+ Only the first method is relevant for authentication. If you provide an implementation of this interface, you can
control exactly how the UserDetails object is created. The first parameter is an instance of Spring LDAP's
DirContextOperations which gives you access to the LDAP attributes which were loaded.
The username parameter is the name used to authenticate and the final parameter is the list of authorities