My Oracle Support Banner

OAAM 11g Fails To Make NAP API Call To The OAM 12 For Authentication (Doc ID 2548471.1)

Last updated on JUNE 02, 2019

Applies to:

Oracle Adaptive Access Manager - Version and later
Information in this document applies to any platform.


On : version, Integration with OAM

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 to test with Webgate_IDM agent.

The same integration works fine when using the TAPScheme only for step up authentication.

Error on OAAM diagnostic log: Server reported that incorrect NAP version is being used, while client attempted to communicate using NAP version 3. See server log for more information.

Error on OAM diagnostic log: Exception encountered while processing the request message for agent {0} at IP {1} Request message {2} :[[ Partner: Webgate_IDM is registered with version Runtime version of agent is different: 10.* .Agent will not be able to communicate with the server

The issue can be reproduced at will with the following steps:
1. Access protected resource
2. Provide username
3. Provide Password




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.