IdP Authenticating to two independent LDAPs with 2 different attribute resolvers

[Peter Schober]

* bleb1982 <btl at fischerinternational.com> [2014-07-16 21:33]:
> IdP Authenticating to two independent LDAPs using stacked login handler, how
> do we tell the attribute resolver to use a specific data connector based on
> the login handler that was used.

See the thread "attribs from db what jaas uses" from 3 weeks ago.
Basically, the use case doesn't make any sense.  If you can't
guarantee non-overlapping usernames (same username representing
different subjects in different data sources) in those directories,
you even fail at authentication and resolution doesn't even enter the
picture (see aforementioned thread for full explanation).
And if you can guarantee that either overlap is null /or/ same
username means same subject, you don't need care about the source
during authentication and can pull data from all existing data
sources -- unless this is really about optimization and very badly
performing data sources, possibly over slow and unreliable links?

But since you mentioned having one Login Handler per SP maybe this all
points more at rather having one IDP per user store?  You don't
mention the actual use case, of course, only that you want things to
work the way you said. Is this about virtualized IDPs/IDP hosting
really?
-peter