See #256633: LDAP Auth, multiple domains, same usernames

Ran across this. Seems like a viable thing to design for. In this case I think it implies multiple ldap_authentication configurations (one for each ldap server/ldap domain).

Do we need to design for this?

Comments

johnbarclay’s picture

Version: 7.x-1.x-dev » 7.x-2.x-dev
fedbccer’s picture

Thank you for thinking about this feature.
For me is essential. I cannot use LDAP without.
And I think is essential for the adoption of Drupal in the Enterprise market.

My organization is base on a Microsoft Active Directory forest, with
- one parent domain: example.net
- many child domains: child_1.example.net, child_2.example.net, ..., child_n.example.net
- different domains in thrust relationship: trustdomain_1.org, trustdomain_2.com, ..., trustdomain_n.net

I would like to help the LDAP project testing this feature as soon as is available

johnbarclay’s picture

I marked #1402206: LDAP Server: Need to be able to differentiate ldap servers on logon and 2 users with same username but different ldap as duplicate. Both involve the user indicating what ldap they are authenticating against in some way.

Jean Gionet’s picture

has any progress been done in supporting this feature?

We are currently migrating to a new domain and we are in need of supporting multiple domains with the same usernames on both servers.

johnbarclay’s picture

Status: Active » Postponed
Media Crumb’s picture

Has anymore thought been given to this idea? It seems common place.

shawn_smiley’s picture

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:

zeezhao’s picture

@johnbarclay - is this similar to the issue we have in D6 ldap_integration - see:
http://drupal.org/node/1694726

Thanks

johnbarclay’s picture

Status: Postponed » Closed (duplicate)