Oracle Access Manager 12.2.1.3: 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 12.2.1.3.220113 and laterOracle Adaptive Access Manager - Version 11.1.2.3.0 to 11.1.2.3.0 [Release 11gR2]
Information in this document applies to any platform.
Symptoms
On : 12.2.1.3.220113 version, Upgrade Patching and Maintenance
OAM - OAAM integration broke after upgrading to OAM 12.2.1.3.
Customer have OAM 11.1.2.3 and OAAM 11.1.2.3. integrated environment, and upgraded the OAM environment to OAM 12.2.1.3. Initially OAAM 11.1.2.3 and OAM 11.1.2.3 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#11.1.2.0.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.>
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 |