template attribute definition possible bug?

[Athanasios Douitsis]

On Tue, Nov 3, 2015 at 11:29 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:

> The trick is that the SourceAttribute ID is only relevant if the
> dependency is a data connector. If it's an attribute definition, the
> SourceAttribute doesn't matter, it simply pulls the values from all the
> dependent attribute definitions and merges them together as the value of
> the SourceAttribute.
>

Yes that was my original hypothesis, source attribute name doesn't have any
effect when dealing with attributes as sources.


>
> That's what you're seeing. The gist is that layering Template on top of
> *any* AttributeDefinition is pathological.
>

That settles it. You may want to adjust the example in the wiki of idpv2
which lists a couple of attributedefinition dependencies in a template.


>
> My use case locally is on top of a DataConnector. In that case, the
> SourceAttribute ID is applied to pull that *specific* attribute out of the
> connector. Which is what you expect to get.
>
> That's the "bug".
>
> I don't know if it's fixable, but Rod and I might need to huddle on this
> in the context of V3.
>





-- 
Athanasios Douitsis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20151103/8a08c8ad/attachment.html>