Two AD data connectors issue with Attribute-resolver

[IAM David Bantz]

I have a number of attributes that need to be treated this way - that is,
the attribute may be populated in source A and/or B.

I need to be clear on the business rules about the attribute and sources
then incorporate those rules in a script in the attribute resolver:
  - if one of the sources has a value, is it authoritative (can I ignore a
result from the other)
  - if A and B have different values, which has precedence (or do I send
multiple values)
  - if neither source has a value, what, if anything, will I release

David

On Wed, Oct 14, 2015 at 12:09 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:

> On 10/14/15, 4:00 PM, "users on behalf of Colon, Joseph" <
> users-bounces at shibboleth.net on behalf of JColon at APUS.EDU> wrote:
>
>
>
> >Thanks for the info Scott,
> >
> >So if I have 2 domains, AD1 and AD3.  Is there any way to return an
> attribute like "mail" back to the SP no matter which domain the user exists
> in?
>
> There are usually a dozen ways to do anything with the resolver. Failover
> connectors running in sequence is one way, another would be using separate
> attributes from each domain and then merging the results together.
>
> -- Scott
>
> >
> --
> 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/20151014/166cfbe1/attachment-0001.html>