duplicate attribute value issue in idp 2.3.3

[Chad La Joie]

Okay, so looking at the code, this bug seems to apply only to those
attributes whose values are XMLObjects (that is, whose values are
known to be XML) and for which multiple filter policies release the
same value(s) within a given request.

In practice, the only attribute this is applies to (unless you have
some custom attribute encoders) are targeted IDs being encoded as SAML
NameIDs (the format everyone should be using at this point).  The
quick fix is what Arjuna said: move the release of that attribute out
to its own policy.

Given the limited scope and ease of mitigating the problem I am not
going to do an immediate IdP release for this unless additional errors
show up that I haven't yet spotted in the code.

On Tue, Aug 2, 2011 at 09:47, Chad La Joie <lajoie at itumi.biz> wrote:
> I don't know yet.  I'm right in the middle of something else so I
> haven't looked at the code.  But if you can't have multiple policies
> dealing with the same attribute that is definitely a bug.
>
> On Tue, Aug 2, 2011 at 09:43, Cantor, Scott E. <cantor.2 at osu.edu> wrote:
>> On 8/2/11 9:35 AM, "Chad La Joie" <lajoie at itumi.biz> wrote:
>>
>>>Okay, that would be a bug and I don't think my test environment has
>>>any cases where multiple policies cover overlapping attributes, so
>>>that would be why I didn't see it.
>>
>> Is it specific to XMLObject as AttributeValue, or does it show up using
>> the NameID encoder too? I'm guessing the former.
>>
>> -- Scott
>>
>> --
>> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
>>
>
>
>
> --
> Chad La Joie
> www.itumi.biz
> trusted identities, delivered
>



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