LDAP Hybrid User Access

The is an authentication mechanism which authenticates users against an LDAP server and stores the role in the database. It does not create an administrative account on module initialization on the LDAP server, however it uses an internal administrative account 'i2ce_admin' with password as defined below. It is designed so that default values will work well with authenticating against a read-only active directory server.

This user access mechanism is implemented by the I2CE_UserAccess_LDAP_DB class.

Configuration

To use the default user authentication, you need to enable the module and set an initialization string.

Enabling the Module

To enable, just make sure you have: <source lang='xml'>

<requirement name='UserAccess_LDAP_Hybrid'>
  <atLeast version='4.0'/>
  <lessThan version='4.1'/>
</requirement>

</source>

Initialization String

The initialization string is sent to I2CE::initialize() in the index.php as the fourth argument, $user_access_init. This string must be prefixed with the 'LDAP://. What follows take any of the following formats:

• null: The is the default value and means that we use the default DN (distinguished name) for querying and authenticating users
• a JSON encoded string: The data to is a JSON enocode string of optional configuration value for the user access. The JSON encoded data has the following keys:
  • userDB: **userDB: The name of the database where the user_table table lies. Defaults to current database
  • user_table: Defaults to 'user_ldap' the table where user roles and id's are stored
  • host: Defaults to 'localhost' The hostname where the openLDAP server lives
  • port: The port openLDAP is listening on. Defaults to 389
  • ldap_user: The user to attempt to bind the ldap connection to. Defaults to 'admin'. If empty we do an anonymous connection
  • ldap_pass: The password to attempt to bind the ldap connection with. If this value is not set, it is the same password used for the database connection.
  • dn: The DN used to query against. Defaults to 'dc=localhost'
  • people: The qualifier to query people against. Defaults to 'People'.
  • person_objectClass: defaults to 'inetOrgPerson'
  • encrypt: how the password is stored on the openLDAP server. Default is SSHA. Possible values are:
    • 'plaintext'
    • 'SHA'
    • 'SSHA'
  • salt: the salt to use for encryption (if needed). Defaults to none.
  • p_details: associative array of the user details that are querriable against People.Defaults as follows:
    • firstname:givenName
    • lastname:sn
    • email:mail
    • commonname:cn
    • locale:Preferred Local
  • p_detail_names: associative array of the display names of user details that are querriable against People.Defaults as follows:
    • firstname:Firstname
    • lastname:Surname
    • commonname:Common Name
    • email:E-mail
    • locale:preferredLanguage
  • can_change_pass: defaults to false
  • can_create_user: defaults to false
  • can_edit_user_details: defaults to false
  • can_edit_role: defaults to true
  • admin_user: The LDAP internal (not stored on LDAP) username for an administrative account. If not set, it uses 'i2ce_admin'
  • admin_pass: It is the password for an administrative account with username 'administrator'. This account is not authenticated against LDAP. If this value is not set, it is the same password used for the database connection.
  • admin_details: associative array of the details for the admin user. Defaults to be as follows:
    • firstname: System
    • lastname: Administrator
    • email: root@localhost
    • locale: en_US
    • commonname: Admin

For example:

LDAP_DB://

would be a minimal initialization string needed to authenticate against. For the examples below, you would use:

 LDAP_DB://{"dn": "dc=moh,dc=example,dc=org"}

LDAP Directory Structure

Example Entries

A user could be represented as:

   dn: uid=litlfred, ou=People, dc=moh,dc=example,dc=gov
   sn: Leitner
   givenName: Carl
   cn: Carl Leitner
   userPassword: {SSHA}DkMTwBl+a/3DQTxCYEApdUtNXGgdUac3
   email: cleitner@intrahealth.org

User roles be unique on the pair (username, software-component) and there may be software component specific information to share,

   dn: uid=litlfred, cn=ihris-manage, ou=Application, dc=moh,dc=example,dc=gov
   role: hr_staff
   appid: 25
   #preferred locale is specific to ihris-manage based on the available locales
   locale: he_IL
   locale: en_US
   
   dn: uid=litlfred, cn=ihris-qualify, ou=Application, dc=moh,dc=example,dc=gov
   role: admin
   appid: 25
   #preferred locale is specific to ihris-qualify based on the available locales
   locale: en_US
 
   dn: uid=litlfred, cn=dhis2, ou=Application, dc=moh,dc=example,dc=gov
   role: guest
   appid: 42

Passwords

We will use SHA and salted SSHA. For a php implementation see this and this