Box integration and the attribute resolver

[Robert Roll]

> You basically don't specify soureAttributeID at all and include two
> separate attribute definitions as Dependency elements, and it should pull
> the values from each one and merge them.

  Cool, let me try working that angle for a while...

Thanks,

Robert

________________________________________
From: users-bounces at shibboleth.net [users-bounces at shibboleth.net] on behalf of Cantor, Scott [cantor.2 at osu.edu]
Sent: Monday, June 16, 2014 11:08 AM
To: Shib Users
Subject: Re: Box integration and the attribute resolver

On 6/16/14, 12:56 PM, "Robert Roll" <Robert.Roll at utah.edu> wrote:

>> Shouldn't, just create two and then a third that sources the other two.
>
> Could you explain this ? If not specifying two soureAttribute ID's I'm
>not sure
>how to source two into one ?

You basically don't specify soureAttributeID at all and include two
separate attribute definitions as Dependency elements, and it should pull
the values from each one and merge them.

The concept of a source ID is for data connector dependencies, it doesn't
really apply to attribute definitions as dependencies.

-- Scott


--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net