The plugin tracks changes affecting users, groups or projects and propagates it simultaneously to a Ldap server. This « enslaved » Ldap server can thus be used for authentication purpose (auth. centralization, SSO) while managing the user's roles and project memberships with Redmine.

Open the configuration from the Administration > Plugins page.

• Active : check it to enable the synchronization
• Ldap base : your LDAP base tree (e.g. dc=localhost)
• User TLS? : check it to secure the communication between Redmine and LDAP
• User DN : user's distinguished name used by the plugin to write in the LDAP, generally something like cn=admin,(your ldap base)
• Password : the user's password
• Ldap users base DN : the tree base in which the users will be stored, relative to the LDAP base
• Ldap groups base DN : the tree base in which the groups will be stored, relative to the LDAP base
• Ldap projects base DN : the tree base in which the projects will be stored, relative to the LDAP base

Warning : the plugin has only been tested with OpenLDAP!

User synchronization:

Each time a user is created, updated or deleted, the modification is propagated to the configured LDAP server. In LDAP, users are stored as inetOrgPerson and posixAccount objects and distinguished by their UID attribute. Here are the current mappings between Redmine fields and the LDAP attributes of an user :

Group synchronization:

Groups inherit from posixGroup and are distinguished by their CN attribute :

Project synchronization:

Projects inherit from posixGroup and uidObject and are distinguished by their CN attribute :