Box integration and the attribute resolver

Robert Roll Robert.Roll at utah.edu
Mon Jun 16 12:50:29 EDT 2014


I had actually found this URL when googling..

https://lists.internet2.edu/sympa/arc/shibboleth-users/2011-07/msg00044.html

 The key part is:

> I think I want something like:
>
> <resolver:AttributeDefinition id="eduPersonEntitlement" xsi:type="Merge"
> sourceAttributeID="eduPersonEntitlement"
> sourceAttributeID="myspecialattribute">
> ...
> </resolver...>
>
> Merge or equivilent doesn't seem to exist and having two sourceAttributeID
> things throws a schema error :(
> 

  Can one really specify two sourceAttributeID's ?

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 10:43 AM
To: Shib Users
Subject: Re: Box integration and the attribute resolver

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

>It is my understanding that the e-mail addresses are actually stored in
>one area in Exchange and the forward are stored in another. Therefore,
>it seems that to create one releasable attribute, that two attributes will
>actually need to be merged.
>
> I believe that merging two or more attributes still requires scripting.
>Is that true ?

Shouldn't, just create two and then a third that sources the other two.

Scripting is the sole reason Java 8 has broken things, I really would not
advise using them except as a last resort. It's clear that Oracle views
compatibility in scripting as not interesting.

-- Scott


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


More information about the users mailing list