OVD 10g (10.1.4.3) Join View Adapter Uses Incorrect Search Base if Special Characters Are Used
(Doc ID 1359811.1)
Last updated on AUGUST 30, 2023
Applies to:
Oracle Virtual Directory - Version 10.1.4.3.0 to 10.1.4.3 [Release 10gR3]Information in this document applies to any platform.
Symptoms
A base search against an entry containing a special character ( for example a
German umlaut like "ß" , sharp s ) fails with LDAP error 32 via a Join Adapter.
Example:
-b "CN=Userß,ou=my_ou,dc=company,dc=com" -s base "cn=*" dn
The problem does not occur , if the search is executed against the OVD LDAP adapter directly.
The OVD vde.log in trace mode shows for the above search and the following adapter configuration:
adapter root: dc=myovd,dc=com
remote base: dc=company,dc=com
Base:
"CN=Userß,ou=my_ou,dc=company,dc=com"
Scope: 0
Attribs: [dn, cn, description]
Filter: objectclass=*
.
Attrs: [dn, cn, description] [WorkThread# 81]
[2011-05-23 09:39:12,963] DEBUG - BackendJNDI: [#w2003rvm] JNDI Adapter
Search using:
BindDN: cn=admin
Base: "CN=Userß,ou=my_ou,dc=myovd,dc=com"
In this example the search against the backend LDAP server uses "ddc=myovd" instead of "dc=myovd".
Cause
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
Symptoms |
Cause |
Solution |
References |