diff --git a/docs/manual/src/docs/asciidoc/_includes/servlet/additional-topics/ldap.adoc b/docs/manual/src/docs/asciidoc/_includes/servlet/additional-topics/ldap.adoc
index 600114b206..8de9f438a3 100644
--- a/docs/manual/src/docs/asciidoc/_includes/servlet/additional-topics/ldap.adoc
+++ b/docs/manual/src/docs/asciidoc/_includes/servlet/additional-topics/ldap.adoc
@@ -86,7 +86,7 @@ If instead you wished to configure an LDAP search filter to locate the user, you
[source,xml]
----
+ user-search-base="ou=people"/>
----
If used with the server definition above, this would perform a search under the DN `ou=people,dc=springframework,dc=org` using the value of the `user-search-filter` attribute as a filter.
@@ -205,29 +205,28 @@ A typical configuration, using some of the beans we've discussed here, might loo
----
-
-
-
+
+
+
-
-
-
-
- uid={0},ou=people
-
-
-
-
-
-
-
-
-
-
+ class="org.springframework.security.ldap.authentication.LdapAuthenticationProvider">
+
+
+
+
+ uid={0},ou=people
+
+
+
+
+
+
+
+
+
+
----
@@ -242,10 +241,10 @@ To configure a user search object, which uses the filter `(uid=
----
-
-
-
+ class="org.springframework.security.ldap.search.FilterBasedLdapUserSearch">
+
+
+
----
@@ -265,10 +264,10 @@ The creation of the `UserDetails` object is controlled by the provider's `UserDe
----
public interface UserDetailsContextMapper {
-UserDetails mapUserFromContext(DirContextOperations ctx, String username,
- Collection authorities);
+ UserDetails mapUserFromContext(DirContextOperations ctx, String username,
+ Collection authorities);
-void mapUserToContext(UserDetails user, DirContextAdapter ctx);
+ void mapUserToContext(UserDetails user, DirContextAdapter ctx);
}
----
@@ -298,11 +297,10 @@ An example configuration would then look like this:
----
+ class="org.springframework.security.ldap.authentication.ad.ActiveDirectoryLdapAuthenticationProvider">
-}
----
Note that there is no need to specify a separate `ContextSource` in order to define the server location - the bean is completely self-contained.