SAML 1.1 Fails On Second Request With An HTTP 404 Error
(Doc ID 1367207.1)
Last updated on JUNE 10, 2022
Applies to:
Oracle WebLogic Server - Version 10.3.4 to 10.3.6Information in this document applies to any platform.
Symptoms
Using PING as IdP and WebLogic Server as SP (SAML 1.1), the SSO link goes every time to PING IdP to generate a SAML token and then the request goes to WebLogic Server SP. If the link is hit twice while a valid session exists in WebLogic Server, a 404 error will be thrown in Weblogic Server, since an authenticated session is passing a session cookie and WebLogic's SAML filter cannot handle them.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |