Ldapbind to OVD 11g is shown as a search in the backend directory
(Doc ID 1535041.1)
Last updated on NOVEMBER 05, 2019
Applies to:Oracle Virtual Directory - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
Set up an OVD 220.127.116.11 Adapter against a backend directory, such as OUD. The passCredentials is set to Always
However, an ldapbind operation against OVD can be seen in the OUD logs as having been converted a search operation by OVD.
This causes a problem with OUD because it does not subsequently trigger the user's last login time to be updated
Example of Bind against OVD :
$ORACLE_HOME/bin/ldapbind -h <OVD_HOSTNAME> -p <OVD_PORT> -D 'uid=<USERNAME>,ou=People' -w <PASSWORD>
- Gets the following in OUD access log:
25/Feb/2013:06:02:23 +0000 SEARCH REQ conn=54 op=8 msgID=9 base="cn=<USERNAME>,ou=People,dc=<COMPANY>,dc=com" scope=baseObject filter="(objectClass=*)" attrs="userpassword"
25/Feb/2013:06:02:23 +0000 SEARCH RES conn=54 op=8 msgID=9 result=0 nentries=1 etime=2
- Gets the following in the wls_ods1-diagnostic.log after setting the OVD debug to TRACE:32
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