OAM Integrated with OID 11g (up to 11.1.1.6.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 11.1.1.2.0 to 11.1.1.6.0 [Release 11g]
COREid Access - Version 10.1.4.3.0 and later
Information in this document applies to any platform.

Symptoms

Oracle Internet Directory (OID) 11g integrated with Oracle Access Manager (OAM).

Scenario 1:
Basic ldapsearches return nothing / no data / no results, for example:

ldapsearch -h myoidhost.mycompany.com -p 389 -D "cn=orcladmin" -q -s base "ou=admin,dc=mycompany,dc=com" "objectclass=*"

 

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:

(&(objectclass=inetorgperson)(&(uid=my_user)(|(obuseraccountcontrol=activated)(!(obuseraccountcontrol=*)))))

 

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:

dn: cn=dsaconfig,cn=configsets,cn=oracle internet directory
changetype: modify
delete: orclinmemfiltprocess
orclinmemfiltprocess: (objectclass=inetorgperson)

- And apply the file above with ldapmodify:

ldapmodify -h myoidhost.mycompany.com -p 389 -D cn=orcladmin -q -v -f <path/filename above>


Afterwards, all searches worked fine and users can login to Oracle Access Manager (OAM) without problems.


Scenario 2:
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 11.1.1.5 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.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms