Spring Security SAML with PingIdentity/ PingFederation, InResponseToField of the Response doesn't correspond to sent message

后端 未结 1 960
南方客
南方客 2021-01-27 09:19

After 1 week of Spring Security SAML Sample App to Ping (PingIdentity) integration effort, I am almost done... now I have an \"InResponseToField of the Response doesn\'t corr

1条回答
  •  悲哀的现实
    2021-01-27 10:07

    This problem is usually caused when JSESSIONID cookie stored when request is generated differs from JSESSIONID found during reception of response. Reason for this is usage of different hostname to send the request and receive the response.

    Any chance both Ping Identity and your application are deployed on localhost? If not, make sure that the hostname you open to initialize the request (e.g. http://localhost:8080/saml/login) is the same where PingIdentity sends the response.

    Past issues with the same error:

    • SP can be accessed by a number of URLs, how to have all the URLs work with an IDP
    • Spring SAML integration with WSO2 Identity server, SAML Message ID not reconised
    • SAMLException: InResponseToField of the Response doesn't correspond to sent message
    • SP can be accessed by a number of URLs, how to have all the URLs work with an IDP

    0 讨论(0)
提交回复
热议问题