Oracle Access Manager 126.96.36.199: OAM - OAAM Integration Broke After From OAM 11g to 12c
(Doc ID 2895950.1)
Last updated on SEPTEMBER 16, 2022
Applies to:Oracle Access Manager - Version 188.8.131.52.220113 and later
Oracle Adaptive Access Manager - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 11gR2]
Information in this document applies to any platform.
On : 18.104.22.168.220113 version, Upgrade Patching and Maintenance
OAM - OAAM integration broke after upgrading to OAM 22.214.171.124.
Customer have OAM 126.96.36.199 and OAAM 188.8.131.52. integrated environment, and upgraded the OAM environment to OAM 184.108.40.206. Initially OAAM 220.127.116.11 and OAM 18.104.22.168 shares same domain, and customer have followed the documentation to split the domain and then upgraded (due to OAAM is not available in 12C).
After the upgrade it is noticed that the resources protected by TAP Scheme (OAAM) are showing repetitive login page after successful authentication. Protected resources are not being presented, instead it is looping back to the Login Pages again.
[2022-09-07T15:47:46.673+00:00] [wls_oaam1] [NOTIFICATION]  [oracle.oaam] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: <ECID>] [APP: oaam_server#22.214.171.124.0] [DSID: <SDID>] User is not authenticated, taking user to the login flow
The following message seen in OAM server diagnostic logs:
<Sep 1, 2022 11:14:07,631 PM UTC> <Error> <oracle.oam.engine.authn> <OAMSSA-12126> <Cannot assert the username from DAP token.>
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