From 6ae7ef0586a46c8601fe102194888650e5fdb0be Mon Sep 17 00:00:00 2001
From: Luke Taylor <luke.taylor@springsource.com>
Date: Wed, 9 Apr 2008 18:04:59 +0000
Subject: [PATCH] SEC-653: Added link to LDAP chapter

---
 src/docbkx/namespace-config.xml | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/src/docbkx/namespace-config.xml b/src/docbkx/namespace-config.xml
index 366bde44be..351b736ffe 100644
--- a/src/docbkx/namespace-config.xml
+++ b/src/docbkx/namespace-config.xml
@@ -251,7 +251,8 @@
         <title>Configuring other Authentication Providers</title>
         <para>
           In practice you will need a more scalable source of user information than a few names added to the context file.
-          Most likely you will want to store your user information in something like a database or an LDAP server. If you have a
+          Most likely you will want to store your user information in something like a database or an LDAP server. LDAP namespace
+          configuration is dealt with in the <link xlink:href="#lpap">LDAP chapter</link>, so we won't cover it here. If you have a
           custom implementation of Spring Security's <classname>UserDetailsService</classname>, called "myUserDetailsService" in your
           application context, then you can authenticate against this using
           <programlisting><![CDATA[