OAAM 11g Fails To Make NAP API Call To The OAM 12 For Authentication
(Doc ID 2548471.1)
Last updated on OCTOBER 14, 2019
Applies to:Oracle Adaptive Access Manager - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
On : 184.108.40.206.0 version, Integration with OAM 220.127.116.11
OAAM Server fails to make NAP API call to the OAM Server for authentication
We have OAAM 11g and OAM 12c deployments in our environment. After protecting a resource on OAM using TAPScheme Authentication level 3, the user enters his username on the first page and password on the next page. Server starts throwing NAP errors after entering the password.
It seems like the NAP API calls to OAM Server is failing due to Webgate version. I have configured oaam_cli.properties to test with the 11g webgate agent.
The same integration works fine when using the TAPScheme only for step up authentication.
Error on OAAM diagnostic log:
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