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

[Cantor, Scott E.]

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