Version: 1.1, by zemic
Developer Last Online: Apr 2010
Category: Integration with vBulletin -
Version: 3.6.5
Rating:
Released: 04-17-2007
Last Update: 05-20-2007
Installs: 38
Uses Plugins
Additional Files
No support by the author.
I've been using Vbulletin for a few years, and have had some great modifications from this community, so having had to recently integrate Vbulletin with LDAP for my University discussion boards I decided to release this as a modification. This is my present to the community .
Description:
LDAP authentication for Vbulletin.
How it works:
This does not modify Vbulletin files or Vbulletin login code in anyway. We simple stick some script infront of the login process so we can validate against LDAP. Below is a breakdown of what this thing does:
First looks to see if login form has been submitted
Checks if it should look up "this" user in LDAP (defined in ldapconfig)
Queries LDAP for the username
If user is returned check if VB MD5 password matches LDAP MD5 password
If it does, check the VB user table to see if the user is already in the table. If yes, update VB user table password with LDAP password by encrypting MD5 password with the users 'salt' key
If not, create a new user in database using VB classes/functions.
If user/pass do not match in LDAP then check if user is in VB user table.
If they are, change the password to something random so they cannot login with an old password
If a user is not returned from LDAP, assume the user has registered on the boards in the normal way and dont do anything to the VB user table.
Requirements:
The requirements are based on the system we use. It may / may not work with other Vbulletin versions:
PHP 4.3+
LDAP System
uid (username), mail (email address), and a field containing MD5 password
Installation:
Download and unzip the file
Edit "ldapconfig.php" and then upload into your "includes" folder
Login to Admin CP and Add / Import the product (xml file)
Extra Info / Future Plans / Help:
This LDAP integration script currently requires you to have an LDAP field with the users password stored as MD5. From my understanding, CRYPT is the default password storage for LDAP so some of you may not have an MD5 field in LDAP with the users password encrypted as MD5.
It would be possible to modify the script to check against CRYPT, but it would also require a template edit as the login form converts the password field "onSubmit" to MD5. I did not do this because we already have the MD5 in LDAP as we use it on a number of different system already, and I did not want to change VB templates.
Also, I was unable to find documentation on doing a script / releasing a modification, so in future if someone could explain to me or change the script slightly to allow editing of LDAP configuration file within ADMIN CP interface, that would be great. This would also mean not having to upload a file into the includes folder.
I'm sure there will be something I havent thought of, or will make it easier if this script had this and that, so feel free to post your ideas, and suggestions on improving this modification.
Important Info:
Hack is provided free of charge (but if you really want to get rid of money PM me ). I make no guarantee it will work on your system, but it does on mine with 15,000 users .
Version:
1.1 - You can now specify the field to authenticate against in ldapconfig.php (19/05/2007)
1.0.1 - Corrected 'mysql_num_rows' query to use VB DB class call (19/04/2007)
(Redirected from LDAP)
Jump to: navigation, search
The Lightweight Directory Access Protocol, or LDAP (IPA: [ˈɛl d?p]), is an application protocol for querying and modifying directory services running over TCP/IP.
A directory is a set of information with similar attributes organized in a logical and hierarchical manner. The most common example is the telephone directory, which consists of a series of names (either of a person or organization) organized alphabetically, with an address and phone number attached.
An LDAP directory often reflects various political, geographic, and/or organizational boundaries, depending on the model chosen. LDAP deployments today tend to use Domain Name System (DNS) names for structuring the topmost levels of the hierarchy. Deeper inside the directory might appear entries representing people, organizational units, printers, documents, groups of people or anything else which represents a given tree entry (or multiple entries).
Its current version is LDAPv3. LDAPv3 is specified in a series of IETF Standard Track RFCs as detailed in RFC 4510.
Quote:
Maybe I will install it, when I know what it is
It is one of those things that if you don't know what it does, you don't need it.