template attribute definition possible bug?

[Cantor, Scott]

On 11/3/15, 4:11 PM, "users on behalf of Athanasios Douitsis" <users-bounces at shibboleth.net on behalf of aduitsis at gmail.com> wrote:



>Slightly modifying the example from the gist Rod suggested, this actually works to my dismay:
>
>        <resolver:Dependency ref="mapped1" />
>        <resolver:Dependency ref="mapped2" />
>        <Template>
>                  <![CDATA[${babadook}:${jabberwock}]]>
>                </Template>
>        <SourceAttribute>babadook</SourceAttribute>
>        <SourceAttribute>jabberwock</SourceAttribute>
>
>I assure you, I haven't ever used the IDs babadook or jabberwock in connection with shibboleth up to this point :). And yet I get back 4 values, A2V1:A2V1 , a1v1:a1v1 , a1v2:a1v2 , A2V2:A2V2. Talk about weird. I am noting this in the hopes of this  proving useful in future debugging by anyone.

Hmm. I'll have to see what the dependency pulling code is doing on a non-existent attribute ID. Perhaps that is the bug. And of course if you have a dependency with only a subset of the attributes in it, that would be equivalent. I didn't follow your meaning, now I think I do.

>I totally respect that you are not going to deal with idp2 or openjdk for that matter. 

I wasn't going to look just to review how the code worked, but now that I have a specific thing to check it for, that's fine. Or Brent will look at it later.

The above just can't be right, so I suggest you file a bug.

-- Scott