Ldapbind to OVD 11g is shown as a search in the backend directory
(Doc ID 1535041.1)
Last updated on MARCH 08, 2017
Applies to:Oracle Virtual Directory - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
Set up an OVD 18.104.22.168 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 ovdhost.au.oracle.com -p 6501 -D 'uid=John Garza,ou=People' -w mypasswd
- Gets the following in OUD access log:
25/Feb/2013:06:02:23 +0000 SEARCH REQ conn=54 op=8 msgID=9 base="uid=John Garza,ou=People,dc=au,dc=oracle,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
BindDN: cn=John Garza,ou=People
Base: cn=John Garza,ou=People,dc=au,dc=oracle,dc=com
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!