This blog post provides an introduction to the Oracle Unified Directory (OUD), Enterprise User Security (EUS), and its integration. An index of all future posts on OUD and EUS integration will be available here.

What is EUS?

• Oracle’s EUS enables one to manage database users across the enterprise from a centralized location.
• Users connect to the Oracle Database by providing credentials stored in the OUD. The database executes LDAP search operations to query user-specific authentication and authorization information.

Benefits of EUS:

• Improved Productivity
  • Frees user from needing to remember multiple database login names and passwords. Time spent on password reset requests is saved.
  • Saves database administrators’ time. DBAs do not need to manage the same user many times (i.e., in multiple databases).
• Audit & Compliance
  • Eliminates need to examine each database individually to find out who has which privileges.
• Security
  • Makes it easy to verify that user access to all databases is disabled and to ensure compliance with password policy requirements.
  • With EUS, user access can be disabled or removed with a single click or action.

High-level steps for EUS & OUD integration:

We can categorize this process into three steps:

1. Preparing the OUD
2. Preparing the database
3. Associating enterprise identities with the database

Preparing the OUD:

Scenarios:

1. User identities stored in the OUD
2. User identities stored in an external, LDAP-compliant directory service with the OUD used as a proxy server

In a series of posts, I will cover detailed steps of both the above-mentioned integration scenarios. Please click the links below for respective blog posts:

Scenario 1: User identities stored in the OUD
Scenario 2: Using the OUD as a proxy server

Preparing the database:

Database preparation involves configuring and registering the OUD with the database. It can be achieved by using a GUI method or a command line tool.

For the GUI method, click here.

Associating OUD identities with the database:

After preparing the OUD and the database for EUS, users from the directory can be authenticated to the database. However, they have to be associated with a schema in the database. This can be achieved by using Database Control or a command line tool called EUSM.

For Database Control or the EUSM tool and various scenarios, refer to this link.

Troubleshooting

Commonly seen errors during EUS integration are discussed here.

Need help?

Do you have an EUS OUD integration project? Or, are you migrating from OID to OUD?

If you need consulting help, please reach us at support@ziontech.com.

433