Weird issues validating prescoped attribute values in Shibboleth SP 2.5.5

[Nick Roy]

SMH.  My attribute resolver for eduPersonScopedAffiliation was using Saml2String instead of Saml2ScopedString.



Nick

On 11/6/15, 8:12 AM, "users on behalf of Nick Roy" <users-bounces at shibboleth.net on behalf of nroy at internet2.edu> wrote:

>Thanks, I will dig into the IdP config further.
>
>
>
>Nick
>
>On 11/5/15, 5:22 PM, "users on behalf of Cantor, Scott" <users-bounces at shibboleth.net on behalf of cantor.2 at osu.edu> wrote:
>
>>On 11/5/15, 4:24 PM, "users on behalf of Nick Roy" <users-bounces at shibboleth.net on behalf of nroy at internet2.edu> wrote:
>>
>>
>>
>>>  When I set this back to ScopedAttributeDecoder, the values get rejected as being unscoped:
>>>2015-11-05 13:09:42 WARN Shibboleth.AttributeDecoder.Scoped [1]: ignoring unscoped AttributeValue
>>>2015-11-05 13:09:42 WARN Shibboleth.AttributeDecoder.Scoped [1]: ignoring unscoped AttributeValue
>>
>>That's pretty much self-explanatory, your issue is with the IdP.
>>
>>>I'm wondering if the IdP is ripping the scope off of the eduPersonScopedAffiliation.  If it's doing this, why isn't it doing the same with ePPN?
>>
>>No idea, but it's not configured correctly.
>>
>>-- Scott
>>
>>-- 
>>To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
>-- 
>To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net