Attributes being removed from SAML1 Service Provider because they cannot be encoded.

[Arjuna Scagnetto]

I've seen exactly the same problem some weeks ago.

Are you sure that you are releasing the transientID?

in resolver and in filter.

Arjuna


On 02/08/2011 17.25, Cantor, Scott E. wrote:
> On 8/2/11 11:18 AM, "Khanna, Sumit (khannast)" <khannast at ucmail.uc.edu>
> wrote:
> 
>> We¹re having a problem with a SAML1 Service Provider
>> (https://soadev.nih.gov/FederationGateway). When we attempt to login, I
>> can see that our IDP is pulling and preparing to encode the attributes we
>> allow for InCommon. The attributes come up in the uApprove screen to, but
>> when we redirect back to the SP, the logs say that it can¹t encode our
>> attributes using the SAML1 encoder.
> 
> As a NameIdentifier, no. There's no reason they should be.
> 
>>  I¹ve also included part of our attribute-resolve below. Are our SAML1
>> AttributeEncoders correct or should those xsi:type attributes be
>> something else?
> 
> No, not really.
> 
> -- Scott
> 
> --
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net