attribs from db what jaas uses

[David Bantz]

Not in any way countering Nate’s cautions, I’m not sure the case is clear.
I understand you to state your users may appear in two sources, 
and either may authenticate them.  If users may appear in both sources,
and your authentication configuration is to fail over, wouldn’t that set up
scenarios confusing to everyone:  If I usually am authenticated against
source A, but occasionally for whatever reason fail over to source B, then
from what you say you want to configure, the resolved/released attributes 
will be different.  A user (or relying service) won’t have a clue what “changed” 
or possibly “broke.”

David Bantz

On Mon, 23 Jun 2014, at 14:33 , Szerb, Tamas <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>
> --
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20140623/81204ed0/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: Message signed with OpenPGP using GPGMail
Url : http://shibboleth.net/pipermail/users/attachments/20140623/81204ed0/attachment-0001.bin