This module allows FlightPath to connect to an LDAP server (Lightweight Directory Access Protocol). This allows users to reuse their campus usernames and passwords with FlightPath.

How it Works:
Normally when a user logs in, FP checks the password in the users table. With this module enabled, FP will first attempt to establish an LDAP connection, and look for the user there. If it finds the user, it will the create a local entry in the users table, as well as either the faculty or students tables, depending on the type of user logging in. No passwords are saved, instead, dummy passwords are stored in the local tables.

Requirements:

• Since FlightPath requires all users to have a numeric ID (called a CWID or Campus-Wide ID in FlightPath), each LDAP user must have a CWID assigned to them as an LDAP attribute. In the settings for this module, you will specify which field to look in for each user's CWID. If your users do not already have something like a CWID in their LDAP attributes, you may need to create a routine which handles this for your LDAP server.
• FlightPath needs to know if users are either faculty or students. Therefor, each LDAP user must have an attribute in LDAP which defines whether they are a faculty member or a student. This can be as simple as an attribute called "is_student" and it can be set to either "yes" or "no". Or, it can be a certain string to look for within any field (including dn). In the settings for this module, you define a simple check on your defined field, and tell FlightPath what value to look for.