Scarab commit: svn commit: r10546 - trunk/xdocs/howto/ldap-howto.xml

Author: hair
Date: 2008-04-30 00:49:33-0700
New Revision: 10546

Modified:
   trunk/xdocs/howto/ldap-howto.xml

Log:
Fix to the documentation, the property everywhere else is scarab.login.ldap.synchronizeOnStartUp 
 (uppercase U in Up)


Modified: trunk/xdocs/howto/ldap-howto.xml
Url: http://scarab.tigris.org/source/browse/scarab/trunk/xdocs/howto/ldap-howto.xml?view=diff&rev=10546&p1=trunk/xdocs/howto/ldap-howto.xml&p2=trunk/xdocs/howto/ldap-howto.xml&r1=10545&r2=10546
==============================================================================
--- trunk/xdocs/howto/ldap-howto.xml	(original)
+++ trunk/xdocs/howto/ldap-howto.xml	2008-04-30 00:49:33-0700
@@ -11,11 +11,11 @@
 
 
 <section name="Enabling LDAP Authentication">
-<p>

+<p>
 Since B21, Scarab is able to authenticate users against an LDAP server. To do 
 this we use the JAAS authentication method to authenticate the username/password
 pair and a new security service which is derived from the standard database 
-based ScarabDBSecurityService. 

+based ScarabDBSecurityService. 
 </p>
 <p>
 The principle is to create the user <strong>on the fly</strong> in case the user
@@ -105,21 +105,21 @@
 the startup time within reason. On the machines this was tested there id an 
 additional second startup time for every 100 users coming from an LDAP server
 on the LAN. 
-</p>

-<p>

-In the build.properties file, include the following properties:

+</p>
+<p>
+In the build.properties file, include the following properties:
 </p>
 <pre>
-	# enable the ldap synchronization

-    scarab.login.ldap.synchronizeOnStartup=true
+    # enable the ldap synchronization
+    scarab.login.ldap.synchronizeOnStartUp=true
     
     # the following parameters are only used 
-    # when synchronization is enabled

+    # when synchronization is enabled
     scarab.login.ldap.providerFactory=com.sun.jndi.ldap.LdapCtxFactory
     scarab.login.ldap.providerUrl=ldap://localhost/
     scarab.login.ldap.ldapQuery=(objectClass=posixAccount)
     scarab.login.ldap.baseDn=dc=example,dc=com
-    scarab.login.ldap.loginAttribute=uid

+    scarab.login.ldap.loginAttribute=uid
 </pre>
 <p>
 Normally there is no need to change the provider factory. The providerUrl must 
@@ -128,7 +128,7 @@
 might cause security holes because of the weak password on dummy accounts. The 
 baseDn points to the start position in the tree from where the recursive search 
 using the ldapQuery starts. Since different schemas use different attributes to 
-map the login name too, this can be defined using the loginAttribute property.

+map the login name too, this can be defined using the loginAttribute property.
 </p>
 </section>
 <section name="Limitations">
@@ -172,6 +172,6 @@
   <li>might be more logical to place the synchronizer as a separate service.</li>
 </ul>
 </p>
-</section>

+</section>
 </body>
 </document>