Differences from version 12 to 16



@@ -1,6 +1,7 @@

 LDAP is the Lightweight Directory Access Protocol, and provides user authentication via an LDAP server. Use of the plugin requires that both PEAR:Auth and the php ldap module are installed in your web server setup. In addition, obviously, an ((LDAPServerConfiguration|operational LDAP server)) is also required.
 
-Ubuntu/Debian Example:^apt-get install php-auth php-ldap^Note for v2.6: ^You must also uncomment ./users/auth/ldap/auth.php line 15. This allows the PEAR::Auth module to be found on your system. Oops; LDAP support is broke in 2.6, working on it now...^
+Ubuntu/Debian Example:^apt-get install php-auth php-ldap^
+Note for v2.6: ^LDAP in the 2.6 release is broken, but the LDAP auth module has been completely rewritten and is fully functional in CVS.^
 
 [http://www.openldap.org/|The OpenLDAP Project] is a useful starting point for setting up a working LDAP system although alternatives are also available. Most of the Linux distributions will have an LDAP server setup that can be enabled if required.
 

@@ -9,7 +10,7 @@

 
 {attachment id=992 size=medium}
 
-The LDAP host and port entries should be self explanatory, and point to the machine hosting your ldap server. The LDAP Base DN will also become understandable. It provides a unique name for the top level of the data, and should be distinct from other sites so that several ldap servers can be combined at a higher level. Normal practice is to use the domain name of the site that you are managing, but this is not essential.
+The LDAP host and port entries should be self explanatory, and point to the machine hosting your ldap server. The LDAP Base DN will also become understandable. It provides a unique name for the top level of the data, and should be distinct from other sites so that several ldap servers can be combined at a higher level. Normal practice is to use the domain name of the site that you are managing, but this is not essential. [http://www.idevelopment.info/data/LDAP/LDAP_Resources/DEPLOY_Choosing_a_Base_DN.shtml|This page provides a nice summary on deciding on a base setting]
 
 The LDAP User DN is a little more complex, and possibly does not even need to be set, but it will direct the authentication plugin to the particular branch that contains the 'people' records that we want to scan. If there are more than one user table for a multiple site, this will restrict access to the section we currently want to access. ( If the setup is using multisite, then it is anticipated that each area of the site would have their own user table, and would amend the User DN based on the particular site name )
 
Page History
Date/CommentUserIPVersion
23 Apr 2009 (18:19 UTC)
Derek Simkowiak71.231.59.10516
Current • Source
Derek Simkowiak71.231.59.10515
View • Compare • Difference • Source
Lester Caine81.138.11.13614
View • Compare • Difference • Source
Lester Caine81.138.11.13613
View • Compare • Difference • Source
Lester Caine81.138.11.13612
View • Compare • Difference • Source
Lester Caine81.138.11.13611
View • Compare • Difference • Source
Lester Caine81.138.11.1369
View • Compare • Difference • Source
Lester Caine81.138.11.1367
View • Compare • Difference • Source
Lester Caine81.138.11.1366
View • Compare • Difference • Source
Derek Simkowiak71.231.59.1055
View • Compare • Difference • Source
Derek Simkowiak71.231.59.1054
View • Compare • Difference • Source
Lester Caine81.138.11.1363
View • Compare • Difference • Source
Lester Caine81.138.11.1362
View • Compare • Difference • Source
Lester Caine81.138.11.1361
View • Compare • Difference • Source