Attribute resolver dependency question/issue

[Chad La Joie]

Usually it's something like:
- reading data from LDAP and one or more databases that share
overlapping attributes in different formats
- running the data from each data connector through different
template/scripts/maps in order to get them in to a common format
- merging those values together in to an attribute to be released
- potentially taking that new attribute and creating a scoped one to be released

Often this is done for affiliation or entitlements.

On Fri, May 4, 2012 at 12:42 PM, Christopher Bongaarts <cab at umn.edu> wrote:
> The more complicated branch/merge/multiplex cases for attributes.
>
> On 5/4/2012 11:16 AM, Chad La Joie wrote:
>> Come to mind for what?
>>
>> On Fri, May 4, 2012 at 10:56 AM, Christopher Bongaarts<cab at umn.edu>  wrote:
>>> On 5/3/2012 1:59 PM, Chad La Joie wrote:
>>>
>>>> By having everything "scoped" to the plugin that produces the data you
>>>> can create some fairly sophisticated data processing pipelines in the
>>>> resolver.  One that merge and branch and multiplex data.  Most people
>>>> just want merging behavior which is why all the fixed logic plugins
>>>> (i.e., not the script ones) that we ship have that behavior.
>>>
>>> Any interesting use cases that come to mind for that?  Seems like it
>>> might be a handy capability to use for some situations.
>>> --
>>> %%  Christopher A. Bongaarts   %%  cab at umn.edu          %%
>>> %%  OIT - Identity Management  %%  http://umn.edu/~cab  %%
>>> %%  University of Minnesota    %%  +1 (612) 625-1809    %%
>>> --
>>> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
>>
>>
>>
>
>
> --
> %%  Christopher A. Bongaarts   %%  cab at umn.edu          %%
> %%  OIT - Identity Management  %%  http://umn.edu/~cab  %%
> %%  University of Minnesota    %%  +1 (612) 625-1809    %%
> --
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net



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