Multiple LDAP domains on the same IDP

Losen, Stephen C (scl) scl at
Fri Oct 25 09:16:11 EDT 2019

Hi Adriano,

We are using JAAS with IDP Password authentication. We have three LDAP servers listed in JAAS for password verification. At our site the usernames are standard, so user X on one LDAP server is the same user X on the other two. However, the passwords can differ. Since your two LDAP servers have different naming conventions, JAAS should work fine for you. 

Steve Losen
ITS - Enterprise Infrastructure
University of Virginia
scl at    434-924-0640

-----Original Message-----
From: users <users-bounces at> On Behalf Of Adriano
Sent: Friday, October 25, 2019 8:38 AM
To: users at
Subject: Re: Multiple LDAP domains on the same IDP

Peter Schober wrote
> The main criterion should be (and I'm not sure your above liste was 
> intended to specify this or not) whether userids are either guaranteed 
> to be mutually exclusive to each domain, or -- where the same userid 
> may exist in both domains -- that at least it represents the same 
> person (though that may still cause issues with differing passwords 
> for the two accounts).

Both domains are completly separated. Users from one domain can't be in the second one (as in, they can't be the same "physical" person). As for the actual value of the nameid, the domains have different naming conventions which makes it impossible to have the same value from one domain to another.

Peter Schober wrote
> There's also the question of multiple MS-AD domains in a "forest" (?) 
> where you can authenticate accounts in multiple domains using a single 
> LDAP configuration. But I know nothing about MS.

Both domains are built the same: one forest with a unique domain. So different LDAP configuration required, I suppose.

We tried to find documentations about configuration for multiple domains but had no luck so far. From the infos we could gather, we need to:

-duplicate the file and reference them in the file (done) -Change value according the domains informations ( and (done)

The rest of the configuration seems to be in the ldap-authn-config.xml file, but i haven't seen anything precise for this part... So far seems to be processed by Shibboleth (and is ignored or overriden).

Sent from:
For Consortium Member technical support, see
To unsubscribe from this list send an email to users-unsubscribe at

More information about the users mailing list