Oracle Access Manager 11g R2PS3 (OAM 11.1.2.3) Log Out Fails "Bad Oracle Access Manager Request" After Applying a Bundle Patch 16 (BP16)
(Doc ID 2543460.1)
Last updated on SEPTEMBER 07, 2023
Applies to:
Oracle Access Manager - Version 11.1.2.3.180717 and laterInformation 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.
Symptoms
Oracle Access Manager 11g R2PS3 (OAM 11.1.2.3) Log Out Fails "Bad Oracle Access Manager Request" After Applying a Bundle Patch
- Use case is Two factor AuthN using OTP having DCC WebGate (tunneling).
- Authentication is successful whereas logout results in "Bad Oracle Access Request"
- Error message and cookies aren't destroyed upon logout.
- Applied to the environment : OAM server Bundle Patch 16 11.1.2.3.181016 ... <patch:28492339> and WebGate Bundle Patch 11 11.1.2.3.180717 <patch:27953548>
- From Header trace:
- User accessed: http://<FQ_HOSTNAME>/<PROTECTED_URL>
- Redirected to: https://<OAM_HOSTNAME>:<OAM_PORT>/oam/server/obrareq.cgi?encquery.
- This sets cookie OAMAuthnCookie_<OAM_HOSTNAME>:<OAM_SSL_PORT>=.......... and completes authentication.
- When logout, there is > Failed logout request: https://<OAM_HOSTNAME>/mypage/logout.....This results in "Bad Oracle Access Manager Request".
Changes
Applied <patch:28492339> OAM 16 11.1.2.3.181016
Applied <patch:27953548> Webgate 11.1.2.3.180717
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 |
Changes |
Cause |
Solution |
References |