LDAP *: Case Sensitivity Issues

Will do. I'll try the latest dev release and now I see the beta5 is out - will try that as well.

As far as the upgrade from 6.x to 7, I had reentered all my server details after the upgrade. I had totally uninstalled the latest ladp_integration 6.x version and installed the LDAP Project beta4.

I'll keep you posted on my status. Thanks for your hard work and an awesome module.

That is a good idea. I'll try to squeeze in some time and get at least a basic upgrade doc together.

On a side note, one thing we utilized in the older 6.x versions of the LDAP module is the ability to pull roles from Active Directory into Drupal and then map select roles. This was useful for giving the Webmaster and IT Department an admin role in our websites. We have upwards of 50 roles in our organization (we need each users' roles to be pulled from AD for access capabilities) and it was time consuming to make a key|value pair for each role to be assigned to itself because IT and Webmaster needed admin rights (without forcibly applying them in Drupal. I wanted every new IT user to be granted the admin rights automatically).

I went ahead and applied this change in the ldap_authorization.inc, specifically the _ldap_authorizations_user_authorizations() function. I'd be more than happy to contribute the code to you, it is just a simple foreach loop. If you go forward with this, you may want to add a checkbox or, at minimum, a note of what would happen when the user adds role filters without checking the 'Use LDAP group to drupal roles filtering'.

I'll post the code and explain a little better what I did.

At line 189 in the ldap_authorization.inc file:

    $filtered_ldap_authorizations = array();
    if ($consumer->consumerConf->useMappingsAsFilter) {
      foreach ($consumer->consumerConf->mappings as $mapping_filter) {
        $map_from = $mapping_filter[0];
        $map_to = $mapping_filter[1];
        if (isset($proposed_ldap_authorizations[$map_from]) || isset($proposed_ldap_authorizations[strtolower($map_from)])) {
          $filtered_ldap_authorizations[] = $map_to;
        }
      }
    }
    else {
      $filtered_ldap_authorizations = array_keys($proposed_ldap_authorizations);
    }

I changed the else statement to:

    else {
      $filtered_ldap_authorizations = array_keys($proposed_ldap_authorizations);
      if (is_array($consumer->consumerConf->mappings) && is_array($filtered_ldap_authorizations)) {
        foreach ($consumer->consumerConf->mappings as $mapping_filter) {
          $map_from = $mapping_filter[0];
          $map_to = $mapping_filter[1];

          $map_from_key = array_search($map_from, $filtered_ldap_authorizations);
          if ($map_from_key !== FALSE) {
            $filtered_ldap_authorizations[$map_from_key] = $map_to;
          }
        }
      }
    }

As an example, with the original module, my roles pulled by ldap after logging into our support website are:

• employees
• forums
• web development
• webmaster

Instead of giving the webmaster role admin capabilities, I had created an admin role. After I made the change to the module, the roles I receive are:

• employees
• forum
• web development
• admin

I still receive the roles provided by LDAP and additionally, certain roles were mapped to the admin role. Kind of a best of both world situation.

I have the following in my mapping textarea:

webmaster|admin
information technology|admin

Let me also state, in this example I used LDAP 7.x-1.0-beta5. I'm sure the code will migrate easily to the latest dev release if you choose to implement.

Hello,

I've tested the current 7.x-1.x-dev with the modification you committed and it worked great with one small modification. In the foreach loop, line 224 of 7.x-1.0-beta9+35-dev:

foreach ($consumer->consumerConf->mappings as $mapping_filter) { }

We need to apply drupal_strtolower() to the $mapping_filter array too. If I typed the mapped keys with uppercase characters, they do not relate properly.

I added the array_walk() call inside the foreach. Here's what I have:

        foreach ($consumer->consumerConf->mappings as $mapping_filter) {
          array_walk($mapping_filter,'drupal_strtolower');
          $map_from = $mapping_filter[0];
          $map_to = $mapping_filter[1];
          $map_from_key = array_search($map_from, $filtered_ldap_authorizations);
          if ($map_from_key !== FALSE) {
            $filtered_ldap_authorizations[] = $map_to;
          }
        }

Thanks for the hard work. This module is great.

Yes that sounds good. I think case-insensitive would be the better approach here. You'll see a lot less support tickets I presume.
The fix that will be applied by the patch in comment 10 will solve the need for the strtolower call later, correct?