Oracle Access Manager 11g R2PS3 (OAM 18.104.22.168): Getting "Bad Oracle Access Manager Request" Error After Webgate Patch 27953548 Using Custom Login Page
(Doc ID 2438175.1)
Last updated on MARCH 30, 2021
Applies to:Oracle Access Manager - Version 22.214.171.124.180717 and later
Information in this document applies to any platform.
Oracle is not responsible for instructions/information from 3rd party sites that may be contained in this KM note.
Customer getting "Bad Oracle Access Manager Request" Error After Webgate Patch 27953548 with custom login page.
Customer is getting "Bad Oracle Access Manager Request" error while login to EBS using custom login page:
Customer sees this error after below Patching (July'2018)
- OAM 126.96.36.199 Patch : 27897816 (180717)
- Webgate 188.8.131.52 Patch : 27953548 (180717)
- EnableHostPortValidation = false (WebGate)
- globalHMACEnabled = true (oam-config.xml)
Customer has recently implemented OAM Custom Login to change Enterprise Logo on the OAM Login page and since this change, they had started getting this error.
If they remove the WebGate <Patch:27953548>, then EBS SSO Login is fine with OAM Custom Login Page.
Customer has implemented OAM Custom Login Page using below Support Note :
Oracle Access Manager 11g R2PS3 (OAM 184.108.40.206) How to Configure the OOTB (Out Of The Box) Custom Login Page (<Note:2317415.1>)
Bundle Patches applied
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