OAM 11g: Query Parameter Values In Protected URL Are Decoded After OAM 11g SSO Login
(Doc ID 1451936.1)
Last updated on MARCH 01, 2019
Applies to:Oracle Access Manager - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 11g]
Information in this document applies to any platform.
Access to protected application pages having URLs containing URL encoded query parameters fails if the access causes redirect for SSO login using Oracle Access Manager (OAM) 11g (22.214.171.124 or 126.96.36.199.0). This is because the query parameters have been URL decoded after OAM SSO login.
The problem causes an application error after OAM SSO login because the application expects the query parameters in the application URL to be URL encoded.
For example, the problem can cause errors when opening an Oracle E-Business Suite (EBS) URL from an email notification, e.g.
If OAM SSO login is performed before the protected resource with URL-encoded query parameters is accessed, then there is no error and the page is successfully displayed in the already authenticated session.
The problem is specific to environments OAM 188.8.131.52/184.108.40.206.0 environments with OAM 10g WebGates on the application tiers.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!