Decoded message was not a SAML 1.x Response

[Hanan Teleb]

 Hi All,

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. does it cause the
problem? or it could be related to libcurl upgrade since libcurl updated to
version 7.25.0?

<SingleSignOnService Binding="urn:mace:shibboleth:
1.0:profiles:AuthnRequest" Location="https://idp/oala/sso"/>
        <SingleSignOnService
Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect" Location="
https://idp/oala/sso"/>


any help would be appreciated.
Thanks
-- 
Hanan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20120420/c248ff2a/attachment.html