<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Not in any way countering Nate’s cautions, I’m not sure the case is clear.<div>I understand you to state your users may appear in two sources, </div><div>and either may authenticate them. If users may appear in both sources,</div><div>and your authentication configuration is to fail over, wouldn’t that set up</div><div>scenarios confusing to everyone: If I usually am authenticated against</div><div>source A, but occasionally for whatever reason fail over to source B, then</div><div>from what you say you want to configure, the resolved/released attributes </div><div>will be different. A user (or relying service) won’t have a clue what “changed” </div><div>or possibly “broke.”</div><div><br></div><div>David Bantz</div><div><br></div><div><div><div><div>On Mon, 23 Jun 2014, at 14:33 , Szerb, Tamas <<a href="mailto:toma@rulez.org">toma@rulez.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Hello,<div><br></div><div>Using Shibboleth IdP 2.4, using same (RDBMS) for JAAS (User/Password auth handler and JDBC JAAS plugin) and attribute resolution.</div><div><br></div><div>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?</div>
<div><br></div><div>I'd like to avoid the situation when the database authenticated users' attributes are resolved from LDAP and vice versa.</div><div><br></div><div>Thanks,</div><div><br clear="all"><div>VWOL<br>
Tamas SZERB <<a href="mailto:toma@rulez.org">toma@rulez.org</a>></div>
</div></div>
--<br>To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net">users-unsubscribe@shibboleth.net</a></blockquote></div><br></div></div></body></html>