The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.I have a need for a feature that I'm going to write code for, and I would like to know if you're interested in committing it. The feature is best described via our use case.
All of our Drupal users are available to us via Active Directory. However, we do not manage the AD, and filing a support ticket to get a user assigned a new Drupal role isn't my idea of a good time.
On the other side of the coin, we run our own LDAP server just for our webapps, and it's working to assign Drupal roles to users. However, in it's current implementation, we have to add any user that is referred to by a group on the non-AD server, duplicating data, and creating the need for a sync mechanism.
The optimal solution for us is to create Drupal roles on our own LDAP server, that have uniqueMembers with DN's found on the AD server. The code changes are minimal -- I already have it working via hardcoding it. I just need to make it configurable.
Is this a feature that other users might need?
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 1248116-3-authorization-multiple-servers.patch | 7.72 KB | justintime |
Comments
Comment #1
johnbarclay commentedSeems like a bit of an edge case. I'm happy with it as long as it can be subordinated in the UI.
I feel your pain. We have 2 active directories and our own OUs, but the different permissions and nesting rules for the different ADs and universal, global, exchange, etc group types makes it a mess.
Comment #2
justintime commentedAttached patch implements the above feature. To enable it, you must check the box under II c at admin/config/people/ldap/authorization/edit/drupal_role that is labeled "Search all enabled LDAP servers for matching users. (Enables roles on one server referencing users on another)". The feature defaults to off.
Comment #3
johnbarclay commentedI committed this. Thanks.
Comment #4
justintime commentedMarking as fixed - thanks!