attribs from db what jaas uses

[Nate Klingenstein]

Tamas,

The easy answer to your question is to ensure that the namespaces for each backend are always different, such that a matched username will always appear in only one system.  Then just have two data sources and attributes that depend on both.

If you can't follow that easy approach, there are a number of hard approaches available to you.

You will have to do this association yourself somehow, though, I think.  The IdP, by design, is not architected with a tight bond between authentication and attribute gathering, and there's no other obvious way to me to do this.

Maybe someone on the list has a better idea,
Nate.

On Jun 23, 2014, at 4:33 PM, "Szerb, Tamas" <toma at rulez.org<mailto:toma at rulez.org>> wrote:

Hello,

Using Shibboleth IdP 2.4, using same (RDBMS) for JAAS (User/Password auth handler and JDBC JAAS plugin) and attribute resolution.

I'm lanning to introduce LDAP auth& attrib resolution, but I'd like to know how it is possible to not confuse the backends, so I'd like to make sure that the attributes will be resolved from the database which it was authenticated against?

I'd like to avoid the situation when the database authenticated users' attributes are resolved from LDAP and vice versa.

Thanks,

VWOL
Tamas SZERB <toma at rulez.org<mailto:toma at rulez.org>>
--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net<mailto:users-unsubscribe at shibboleth.net>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20140623/b6dc1483/attachment.html