My Oracle Support Banner

Oracle Access Manager 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 and later
Oracle Adaptive Access Manager - Version to [Release 11gR2]
Information in this document applies to any platform.


On : version, Upgrade Patching and Maintenance

OAM - OAAM integration broke after upgrading to OAM

Customer have OAM and OAAM integrated environment, and upgraded the OAM environment to OAM Initially OAAM and OAM 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.

The following message seen in OAAM server diagnostic logs:

[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#] [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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.