Decoded message was not a SAML 1.x Response

[Cantor, Scott]

On 4/20/12 11:56 AM, "Hanan Teleb" <hanan.ebraheem at gmail.com> wrote:
>
>I have an issue related to saml 1 binding. I am using shibboleth sp for
>protecting online resource. I have shibboleth authentication works
>properly for other customers, but one of customers reported updated Idp
>Entity ID. after updating the Entity ID in the
> corresponding files it is giving samlbindingexecption with error message
>"Decoded message was not SAMl 1.x Response". I did check the log file ad
>everything seems ok as it is sp granted authentication. but in the
>metadata i have for this entity has both of
> shib/Saml1 and SAMl2 binding to the same location.

It's up to the IdP if that works (it doesn't with Shibboleth), but the SP
uses different ACS endpoints for different protocols, and the IdP is
returning a SAML 2 response to the SAML 1 ACS at the SP.

I have no idea what you're doing or what its doing, but that won't work. I
would start by determining what SAML version is being used in the request
to the IdP based on logs, and then see if the problem is the IdP mixing
the protocols or something like that.

>does it cause the problem? or it could be related to libcurl upgrade
>since libcurl updated to version 7.25.0?

Uh, no, sorry.

-- Scott