DN Matching is Ignored When the Search Base is the OVD 11g Adapter's Root (Doc ID 1292484.1)

Last updated on FEBRUARY 21, 2019

Applies to:

Symptoms

OVD 11g

DN Matching doesn't work when a search is performed against the adapter's root. OVD Log file shows the following message

"Match test not applied since [base] is above [base]"

Steps to reproduce the scenario :

• Create a Local Store Adapter with the following structure.
  
  dc=test,dc=com (domain)
  ou=unit10,dc=test,dc=com (organizationalUnit)
  cn=user1,ou=unit10,dc=test,dc=com (inetOrgPerson)
  ou=unit11,dc=test,dc=com (organizationalUnit)
  cn=user2,ou=unit11,dc=test,dc=com (inetOrgPerson)
  ou=unit12,dc=test,dc=com (organizationalUnit)
  cn=user3,ou=unit12,dc=test,dc=com (inetOrgPerson)

• Fill the DN Matching field in Routing tab with regular expression: (ou=unit10)
  That means match only dn's including substring ou=unit10.

• Do the following search with search base "dc=test,dc=com"
  
  ldapsearch -h localhost -p 6501 -D "cn=orcladmin" -w welcome1 -b "dc=test,dc=com" -s one "objectclass=*" dn

• Result:
  ou=unit10,dc=test,dc=com
  ou=unit11,dc=test,dc=com
  ou=unit12,dc=test,dc=com

• Here, DN Matching is not used and OVD log shows the following message

"Match test not applied since dc=test,dc=com is above dc=test,dc=com"

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.