LDAP User: Unable to configure multiple LDAP server for Drupal account provisioning

This was simply a usability and design simplicifacation decision. If it can be done in a way that doesn't make the user interface difficult and the code overly complex, I think this is a useful feature. If its simply querying multiple servers to find the ldap user, it would be quite easy to simply change the server field to checkboxes. If the goal is to get some use fields from one ldap server and others from another, I think it would add a lot of complexity to the UI and code.

Has there been any update on this? I'm also looking for the same feature - to have multiple LDAP servers provisioning Drupal accounts.

No progress on this. The checkbox approach in #1 is the way to go I believe.

If its simply querying multiple servers to find the ldap user, it would be quite easy to simply change the server field to checkboxes.

This was my thinking - changing the radio buttons to checkboxes, and essentially looping through each server until the specified LDAP user is found.

The only complication that I can forsee is "what if the same username exists in multiple domains, but for different users?" - i.e. different companies within the same group, but I'm looking at using NTLM to help out with this. I wonder if it would be worth adding a weight to each defined server so that they are searched in a particular order?

If the goal is to get some use fields from one ldap server and others from another, I think it would add a lot of complexity to the UI and code.

Agreed.

I'm going to be working on this for a Precedent project over the next few days, and would definitely plan on contributing this back, assuming that the client is willing, so I'll be working on the 7.x-2.x branch going forward.

Thanks. Agreed about the conflict/precedence order. Ping me via contact form if I don't get back to you quick enough on any questions or on committing patches.

Thanks - that's much appreciated. Since posting this comment, I thought that if the NTLM extension is working and functional, one of the variables that I believe this provides is the domain that the user is visiting from. If this is the case, then theoretically I should be able to connect directly to the corresponding LDAP server for that domain, rather than going through each in a for loop or something.

The last thing that I was is to have a scenario where a user no longer exists on LDAP Server 'A' because they've left the company, for example, but can still access the site by inadvertently being authenticated by a LDAP Server 'B'.

Any progress on this? I also have multiple active directories I would like to provision against.

Thanks,
Zak

I've got the code and the ldap_ntlm submodule written, I'm waiting on approval from our client to publish it. I'll email them tomorrow and hopefully I'll get a response soon.

Would love to know if there is any movement on this. This is vital to our organization as well.

I am still waiting and hopeful of this functionality as well!

Thanks

Just a note that there seems to be multiple related issues in the queue. While these issues aren't exact duplicates I wanted to list them for reference purposes in hopes that the solution to one of these could address all of them.

The related issues are:

• #1740978: LDAP Authentication and LDAP User: LDAP not allowing to authenticate to multiple servers
• #1923516: LDAP User: Unable to configure multiple LDAP server for Drupal account provisioning (this issue)
• #987324: LDAP Auth, multiple domains, same usernames

This is the issue to follow: #1740978: LDAP Authentication and LDAP User: LDAP not allowing to authenticate to multiple servers