With Oracle Virtual Directory a LDAP adapter can be created which is mapped to either user container ("cn=users,dc=example,dc=com") or root value in LDAP server. It can also be mapped to the tree of the server (dc=example,dc=com). If two different LDAP adapters are created within OVD a user can be searched from both the directories or from a single directory based on the Mapped name space in the OVD.
Below is the use case scenarios depicting the same:
Now from the adapter browser even cn=”changelog” can be seen which doesn’t come under “dc=us,dc=oracle,dc=com” tree in OUD.
Below is the use case scenarios depicting the same:
Create an Adapter with OID/OUD using remote base as “” and
mapped name space to “dc=eus,dc=oracle,dc=com”. It can also be mapped to either tree (dc=oracle,dc=com) or user container (cn=Users,dc=oracle,dc=com).If we have to search the root values also from OID/OUD then map it to "".
Now from the adapter browser even cn=”changelog” can be seen which doesn’t come under “dc=us,dc=oracle,dc=com” tree in OUD.
Create another adapter for Active directory mapping it to
remote base as “dc=dev,dc=oracle,dc=com”.
Now mapping is as below:
OUD/OID:
Remote base: “”
Mapped Name Space: dc=eus,dc=oracle,dc=com
AD:
Remote Base: “dc=dev,dc=oracle,dc=com”
Mapped Name Space: dc=eus1,dc=oracle,dc=com
Now below use cases can be completed using ldapsearch
through OVD.
Usecase:1 Ã Searching a user in
both the directories.
If Ldapsearch is run against “dc=oracle,dc=com” then OVD
will search the user in both the directories.
Searching an OUD user:
Now searching the above user “uid=user.0” through OVD.
Searching an AD user:
Searching the above user “cn=oam” using ldapserach.
Usecase:2 Searching a user in
OUD.
A user can be searched in only OUD using mapped name space
“dc=eus,dc=oracle,dc=com” while searching through OVD.
Usecase:3 Searching a user in
AD.
A user can be searched in AD using the name space
“dc=eus1,dc=oracle,dc=com” while searching through OVD.
Comments
Post a Comment