Last updated on MARCH 08, 2017
Applies to:Oracle Virtual Directory - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
The problem is with OVD 11g (220.127.116.11) release with WLS 10.3.5. Backend LDAP ODSEE 18.104.22.168.
In testing the configuration of OVD adapters a particular ldapsearch was found that would return no entries by OVD. Also, no error returned.
Issuing the same identical search from a putty session, OVD did return the expected entry.
No further information available in OVD logs which tells us what is the difference in both searches (comparing application search with manual command line search)
It is found that the backend ODSEE logs report an error on the search. The search performed by the application 'failed' at backend ldap with an ldap error code 12 but OVD still returned error code as zero(OR no error at the prompt)
Desired outcome: OVD error code must be same as backend ldap error code OR an error should be reported in the OVD logs.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms