OAM Integrated with OID 11g (up to 22.214.171.124.0) - Ldapsearches Return No Results Or Partial Results / OAM Policy Related Functionality Intermittent Failing / OAM 10g API Reports Missing Policies
(Doc ID 1408607.1)
Last updated on MARCH 08, 2017
Applies to:Oracle Internet Directory - Version 126.96.36.199.0 to 188.8.131.52.0 [Release 11g]
COREid Access - Version 10.1.4.3.0 and later
Information in this document applies to any platform.
Oracle Internet Directory (OID) 11g integrated with Oracle Access Manager (OAM).
Basic ldapsearches return nothing / no data / no results, for example:
Or, OAM returns 'Invalid Credentials' for some OID users randomly or intermittently. An OID debug log may sometimes show searches with filter such as below returning nentries=0:
Whereas a few seconds apart, the log shows the same search with same filter returning nentries=1.
The following workaround resolves this problem:
- Create an ldif (text) file with the following:
- And apply the file above with ldapmodify:
Afterwards, all searches worked fine and users can login to Oracle Access Manager (OAM) without problems.
Manually exported all OAM 10.1.4.3 config and policy data from a working OID 10.1.4.3 via ldifwrite to an ldif file, then bulkloaded the data into a newly installed OID 11g 184.108.40.206 with restore option, as per the following Note:
<Document:1295015.1> How to Replicate User, Groups and Oblix data from Production to Pre-Production/QA
Verified the data is the same on the exported and imported OIDs using different methods, i.e., oidcmprec with compare option, ldif file comparison tools, etc.
Even though the data is confirmed to be the same, OAM 10.1.4.3 using OID 11g does not work correctly; there are intermittent problems with OAM functionality and the policies do not work as they should, for example, a user type may not get authenticated, or a functionality behaves as if the policies were not correct. Also, an OAM API to validate the policies (AccessManagerSamples.java) consistently reports missing policies.
If importing the same data into another OID 10.1.4.3 instead, OAM does not have any such problems and continues to work as in the original environment.
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|