OID ldapsearch Not Displaying the Requested Operational Attributes And Their Values (Such As pwdaccountlockedtime, pwdfailuretime, etc) (Doc ID 944222.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Internet Directory - Version 10.1.2 and later
Information in this document applies to any platform.

Symptoms

Ldapsearch filters not showing, or consistently showing, values for requested operational attributes, such as attributes that store time stamps, even though the attributes are verified to be indexed and contain values.  This can also affect custom code, i.e., dbms_ldap or java code searches.

The following or similar symptoms can occur:

Symptom 1:
When searching for locked accounts, the ldapsearch results does not display / return the pwdaccountlockedtime attribute/value pair requested.

Other attributes requested are returned ok in the search results, including perhaps other operational attribute types such as orclguid.

For example:

ldapsearch -h <oid hostname> -p <port> -D cn=orcladmin -w <password> -s sub -b "" "(pwdaccountlockedtime=*)" dn orclguid cn pwdaccountlockedtime

Returns only the first three of the four attributes requested:

cn=user1, cn=Users,dc=mycompany,dc=com
orclguid=73544D1AC3896FB2E040A8C01F183577
cn=user1


Symptom 2:
An ldapsearch requesting a single operational attribute does not return its name/value pair in the
search results.  When requesting an additional attribute, i.e., two or more, then the search returns the expected results ok.

For example, the following ldapsearch does not does not return pwdaccountlockedtime even when the account is locked and the attribute is populated:

ldapsearch -h <oid host> -p <port> -D cn=orcladmin -w <password> myguid=9999 pwdaccountlockedtime
myguid=9999,dc=mycompany,dc=com

But when adding another attribute to be retrieved, then it lists all the expected values ok:

ldapsearch -h <oid host> -p <port> -D cn=orcladmin -w <password> myguid=9999 pwdchangedtime pwdaccountlockedtime
myguid=9999,dc=mycompany,dc=com
pwdchangedtime=20080721112958z
pwdaccountlockedtime=20080728153023z

The same behaviour can happen for other attributes, such as pwdfailuretime for example.

Changes

OID schema defnition default values for the attribute(s) in question were changed. 

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