Why does the Oracle Password Filter Required An AD User With Privileges To Create Subtree Entries? (Doc ID 1290753.1)

Last updated on SEPTEMBER 22, 2016

Applies to:

Oracle Internet Directory - Version: 11.1.0.6 and later   [Release: 11g and later ]
Information in this document applies to any platform.
This applies to OID 10.1.4.3 through 11g

Goal

Why does the Oracle Password Filter require an AD User with Privileges to create subtree entries?
What changes will occur in the AD directory?

Per the documentation:

Microsoft Active Directory User =>

"A user name with read privileges on the entire Microsoft Active Directory DIT and privileges to create an organizational unit and subtree entries under the Microsoft Active Directory base DN. Note that you must enter a user name and not the DN of an administrative user. This value is usually in the form administrator@machine_name."


Reference:

Oracle Fusion Middleware Integration Guide for Oracle Identity Management 11g Release 1 (11.1.1) > Chapter 19 Deploying the Oracle Password Filter for Microsoft Active Directory > Installing and Reconfiguring the Oracle Password Filter for Microsoft Active Directory

Oracle Identity Management Integration Guide 10g (10.1.4.0.1) > Chapter 20 Deploying the Oracle Password Filter for Microsoft Active Directory > Installing and Reconfiguring the Oracle Password Filter for Microsoft Active Directory

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms