SAML 1.1 Fails On Second Request With An HTTP 404 Error
Last updated on DECEMBER 11, 2017
Applies to:Oracle Weblogic Server - Version: 10.3.4
Information in this document applies to any platform.
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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms