You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@vcl.apache.org by bu...@apache.org on 2012/07/27 22:51:31 UTC

svn commit: r827236 - in /websites/staging/vcl/trunk/content: ./ docs/ldapauth.html

Author: buildbot
Date: Fri Jul 27 20:51:31 2012
New Revision: 827236

Log:
Staging update by buildbot for vcl

Modified:
    websites/staging/vcl/trunk/content/   (props changed)
    websites/staging/vcl/trunk/content/docs/ldapauth.html

Propchange: websites/staging/vcl/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Jul 27 20:51:31 2012
@@ -1 +1 @@
-1366532
+1366533

Modified: websites/staging/vcl/trunk/content/docs/ldapauth.html
==============================================================================
--- websites/staging/vcl/trunk/content/docs/ldapauth.html (original)
+++ websites/staging/vcl/trunk/content/docs/ldapauth.html Fri Jul 27 20:51:31 2012
@@ -92,8 +92,10 @@
 </ul>
 <p>This will be referred to as 'vcllookup' on 
 this page. You can skip this step if anonymous binds are enabled on your LDAP server 
-and an anonymous bind will be able to look up the listed items.
-* If your LDAP server is behind a firewall, you will need to allow your VCL web 
+and an anonymous bind will be able to look up the listed items.</p>
+</li>
+<li>
+<p>If your LDAP server is behind a firewall, you will need to allow your VCL web 
 server to access tcp port 636 on your LDAP server</p>
 </li>
 </ul>
@@ -119,10 +121,12 @@ certificate</a>).</p>
 <p>You can verify that the certificate is properly installed using this command:</p>
 <p>openssl s_client -showcerts -CAfile /etc/pki/tls/certs/ca-bundle.crt -connect 
 your.ldap.server.here:636</p>
-<p>If you see "Verify return code: 0 (ok)" at the end of the output then it is 
+<p>If you see \"Verify return code: 0 (ok)" at the end of the output then it is 
 installed correctly. If you see a different return code, then you'll need to 
-troubleshoot the problem.
-<em> You may need to add a line to </em>/etc/openldap/ldap.conf* to point to the 
+troubleshoot the problem.</p>
+</li>
+<li>
+<p>You may need to add a line to <strong>/etc/openldap/ldap.conf</strong> to point to the 
 ca-bundle.crt file. If so, add the following:</p>
 <p>TLS_CACERT /etc/pki/tls/certs/ca-bundle.crt</p>
 </li>
@@ -133,7 +137,7 @@ ca-bundle.crt file. If so, add the follo
 <p>You will need to manually add an entry to the affiliation table in the VCL 
 database. Choose a name for the affiliation. This will be appended to all userids 
 for the affiliation to distinguish them from other affiliations you may configure 
-later. <em>Do not</em> use the Global affiliation for this. Initials or a short name of 
+later. <strong>Do not</strong> use the Global affiliation for this. Initials or a short name of 
 your organization are a good idea. The affiliation name cannot contain spaces. Use 
 the following to add the affiliation, replacing 'EXAMPLE' with the name you chose. 
 Take note of the id from the 2nd SQL statement as you will need it later. It is the 
@@ -190,7 +194,7 @@ this to the attribute to use to search f
 authentication method explaining why they would select this option</li>
 </ul>
 </li>
-<li>Uncomment the <em>require_once</em> line for <em>ldapauth.php</em> toward the bottom of the file</li>
+<li>Uncomment the <strong>require_once</strong> line for <strong>ldapauth.php</strong> toward the bottom of the file</li>
 </ul>
   </div>