invoking data connector dynamically in attribute resolver

[Chad La Joie]

While I am adding this feature to IdPv3 (it's already done actually),
the question I always ask people about this is "Is the feature worth
the complexity?".  Stuff like this makes configurations more complex
and thus more difficult to write and debug.

So, let me ask you the same question, just so I have additional data.
Why do you want to do this?  Are the other data sources really slow or
very limited in capacity?

On Wed, May 23, 2012 at 4:16 PM, Robert A Basch <rbasch at mit.edu> wrote:
> On May 18, 2012, at 9:16 PM, Peter Schober wrote:
>
>> Someone from our constituency used the method described in
>> https://lists.internet2.edu/sympa/arc/shibboleth-users/2011-05/msg00433.html
>
> Thanks, Peter, the multiple attribute authority approach looks promising.  Our
> case may be a bit different from the referenced thread, in that we want to invoke
> an additional set of connectors (i.e. as well as the standard set) for the relying
> parties in question, but that would just make our configuration more cumbersome.
> Another possible issue is that uApprove (which we are looking at, but have not yet
> deployed) apparently can only deal with one attribute authority, but that may not be
> a deal-breaker.
>
> Thanks,
> Bob
>
>
>
> --
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net



-- 
Chad La Joie
www.itumi.biz
trusted identities, delivered