Accessing APEX url in Microsoft Edge Gives "There is no SAML message in the HTTP request, it should be a value of SAMLResponse parameter."
(Doc ID 2815222.1)
Last updated on OCTOBER 21, 2024
Applies to:
Oracle WebLogic Server - Version 12.2.1.4.0 and laterInformation in this document applies to any platform.
Symptoms
On APEX 20.1 environment using WebLogic 12.2.1.4 Federation Services 2.0, Active Directory 2008, and Miicrosoft Active Directory Federation Services 2.0 for SAML configuration, while attempting to access the apex URL in Microsoft Edge, 400, malformed URL error is seen.
The same URL can be accessed successfully in Chrome and FF Browsers.
Upon enabling SAML and HTTP debugs such as
-Dweblogic.debug.DebugSecuritySAML2Atn=true -Dweblogic.debug.DebugSecuritySAML2Lib=true -Dweblogic.debug.DebugSecuritySAML2Service=true -Dweblogic.debug.DebugHttpSessions=true
-Dweblogic.debug.DebugHttp=true
For debug logging :-
-Dweblogic.StdoutDebugEnabled=true
-Dweblogic.log.LogSeverity=Debug
-Dweblogic.log.LoggerSeverity=Debug
Following stack trace is seen:
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 |