OAM Not Able To Access User When User Data Is OVD But Using ODSEE Works Fine
(Doc ID 1539845.1)
Last updated on MAY 24, 2022
Applies to:Oracle Access Manager - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
You are trying to integrate OAM 11.1.2 with OAAM 11.1.2 using Advanced Integration process.
After completing the steps, when you protect a resource with TAPScheme and test it, the OAAM authentication page keeps looping and you don't get the resource page.
You have set the default store to the OVD and same has also been configured for TAPScheme (set the LDAP module used in LDAPScheme to use default store) as mentioned in following section in document but it didn't help:
184.108.40.206 In the Access Manager and OAAM Integration TAP Could Not Modify User Attribute
If you set the default store to embedded LDAP or ODSEE, and point TAPScheme to it, the authentication works fine. The issue comes up only with default store is OVD.
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