When using the normal ldapgroups module, a mapping between LDAP groups (e.g. cn=drupal_adm,ou=groups,dc=example,dc=net) and Drupal user roles (e.g. Admin) is specified in the textbox "Mapping of LDAP groups to Drupal roles". However, when adding or removing users from these groups, the extended_ldapgroups module looks up only the "composed" name (in this case cn=Admin,ou=groups,dc=example,dc=net), i.e. ignores this mapping and thus will fail in adding/removing users, as the group that is looked for does not exist. I'd be happy to see this improved.

CommentFileSizeAuthor
#1 extended_ldapgroups-role_mapping.diff3.46 KBtpfeiffer

Comments

tpfeiffer’s picture

tpfeiffer commented
Status: Active » Needs review
StatusFileSize
new extended_ldapgroups-role_mapping.diff3.46 KB

I am attaching a patch that

  • respects the manually set-up mapping between LDAP groups and Drupal roles instead of composing the LDAP group string from the role name (this may actually be not the intention of this module) and
  • works with multiple base DNs configured in Drupal by just taking the first value.

I'd be happy about feedback and inclusion of this or an improved version in the module.