ZionTech blogging about integration of OUD and EUS

Here are good posts about OUD and EUS integration :

EUS OUD related posts as of now are here:

Advertisements

Using EUSM to manage EUS mappings in OUD

By Sylvain Duloutre on Oct 17, 2013

EUSM is a command line tool that can be used to manage the EUS settings starting with the 11.1 release of Oracle. In the 11.1 release the tool is not yet documented in the Oracle EUS documentation, but this is planned for a coming release.

The same commands used by EUSM can be performed from the Database Console GUI or from Grid Control*.

For more details, search for the document ID 1085065.1on https://support.oracle.com/epmos/faces/DocumentDisplay?id=1085065.1.

The examples below don’t include all the EUSM options, only the options that are used by EUS.

EUSM is user friendly and intuitive. Typing eusm help <option> lists the parameters to be used for any of the available options. Here are the options related to connectivity with OUD :

ldap_host=”gnb.fr.oracle.com” – name of the OUD server.

ldap_port=1389 – nonSSL (SASL) port used for OUD connections.

ldap_user_dn=”cn=directory manager” – OUD administrator name
ldap_user_password=”welcome1″ – OUD administrator password

Find below common commands:

To List Enterprise roles in OUD

eusm listEnterpriseRoles domain_name=<Domain> realm_dn=<realm> ldap_host=<hostname> ldap_port=<port> ldap_user_dn=<oud administrator> ldap_user_password=<oud admin password>

To List Mappings

eusm listMappings domain_name=<Domain> realm_dn=<realm> ldap_host=<hostname> ldap_port=<port> ldap_user_dn=<oud admin> ldap_user_password=<oud admin password>

To List Enterprise Role Info

eusm listEnterpriseRoleInfo enterprise_role=<rdn of enterprise role> domain_name=<Domain> realm_dn=<realm> ldap_host=<hostname> ldap_port=<port> ldap_user_dn=”<oud admin>” ldap_user_password=<oud admin password>

To Create Enterprise Role

eusm createRole enterprise_role=<rdn of the enterprise role> domain_name=<Domain> realm_dn=<realm> ldap_host=<hostname> ldap_port=<port> ldap_user_dn=”<oud admin>” ldap_user_password=<oud admin password>

To Create User-Schema Mapping

eusm createMapping database_name=<SID of target database> realm_dn=”<realm>” map_type=<ENTRY/SUBTREE> map_dn=”<dn of enterprise user>” schema=”<name of the shared schema>” ldap_host=<oud hostname> ldap_port=<port> ldap_user_dn=”<oud admin>” ldap_user_password=”<oud admin password>”

To Create Proxy Permission

eusm createProxyPerm proxy_permission=<Name of the proxypermission> domain_name=<Domain> realm_dn=”<realm>” ldap_host=<hostname> ldap_port=<port> ldap_user_dn=”<oud admin>” ldap_user_password=<oud admin password>

To Grant Proxy permission to Proxy group

eusm grantProxyPerm proxy_permission=<Name of the proxy permission> domain_name=<Domain> realm_dn=”<realm>” ldap_host=<hostname> ldap_port=<port> ldap_user_dn=”<oud admin>” ldap_user_password=<password> group_dn=”<dn of the enterprise group>”

To Map proxy permission to proxy user in DB

eusm addTargetUser proxy_permission=<Name of the proxy permission> domain_name=<Domain> realm_dn=”<realm>” ldap_host=<hostname> ldap_port=<port> ldap_user_dn=”<oud admin>” ldap_user_password=<oud admin password> database_name=<SID of the target database> target_user=<target database user> dbuser=<Database user with DBA privileges> dbuser_password=<database user password> dbconnect_string=<database_host>:<port>:<DBSID>

Enterprise role to Global role mapping

eusm addGlobalRole enterprise_role=<rdn of the enterprise role> domain_name=<Domain> realm_dn=”<realm>” database_name=<SID of the target database> global_role=<name of the global role defined in the target database> dbuser=<database user> dbuser_password=<database user password> dbconnect_string=<database_host>:<port>:<DBSID> ldap_host=<oid_hostname> ldap_port=<port> ldap_user_dn=”<oud admin>” ldap_user_password=<oud admin password>

OUD&EUS Take 2: DB Accounts Proxy-ed by OUD into existing Directories

By Sylvain Duloutre on Aug 27, 2013

This post is the second one of a serie focusing on Enterprise User Security (EUS) and Oracle Unified DIrectory (OUD).

Enterprise User Security (EUS), an Oracle Database Enterprise Edition feature, leverages the Oracle Directory Services and gives you the ability to centrally manage database users and role memberships in an LDAP directory. EUS reduces administration costs and increases security.

DB Accounts Proxy-ed by OUD into existing Directories

Most enterprises already have existing corporate directories in place, and prefer the EUS implementation. An EUS implementation leverages the existing directory infrastructure and user information base without putting in place synchronization between directories. In this way, OUD acts as a real-time interpreter for Oracle database information requests to user data.

Using OUD enables the database to interact with third-party directories. OUD leverages existing user and group information in the existing third-party directory infrastructure by forwarding LDAP requests and responses back and forth to the third-party directory holding user data. User data, database meta-data such as DB registration information, user/role Mappings, and other EUS specific meta-data are stored locally in OUD, without requiring any schema changes to store EUS configuration in the existing third-party directory.

As of release 11gR2PS1, OUD is certified with EUS to support Active Directory, Oracle Directory Server Enterprise Edition, and Novell eDirectory. Working with these products, OUD eliminates user data duplication and synchronization and consequently lowers total cost of ownership (TCO).

  1. Centralizing Accounts into Microsoft Active Directory

You can integrate Active Directory for password-based authentication or integrate Active Directory with Kerberos authentication.

Active Directory Integration for Password-based authentication

Such a scenario requires deployment of an additional component: the OUD Password Change Notification plug-in (oidpwdcn.dll). Microsoft uses a proprietary implementation to hash passwords in Active Directory that is incompatible with the Oracle DB requirements. The OUD Password Change Notification plug-in isnotified when a password change occurs, and stores hashes in Active Directory. The oidpwdcn dll must be installed on every Active Directory domain controller.

Active Directory Schema extension is required to store the hashed passwords.

The database establishes a connection to OUD. OUD retrieves user data (users and groups) from Active Directory. User passwords are retrieved from the hashed password stored by the OUD Password Change Notification plug-in. EUS metadata are stored and retrieved from OUD.

The database version must be 10.1 or later as earlier versions use a different and incompatible password format.

eus_ad[1]

Figure 2: EUS Account management with Active Directory

Active Directory Integration with Kerberos Authentication

In this scenario, Kerberos is used for DB authentication. EUS with DB Kerberos authentication does not require any changes to the database beyond standard EUS configuration. The database establishes a connection to OUD. OUD looks up the requested DB information in Active Directory. All database clients must be Kerberos-enabled to use this option. This capability is only supported with DB version 10.1 or higher.

The database establishes a connection to OUD. OUD retrieves user data (users and groups) from Active Directory. EUS metadata are stored and retrieved from OUD. Access to the hashed user password is not required, so no schema extensions and no Password Change Notification dll have to be deployed on Active Directory.

eus_kerberos[1]

Figure 3: EUS Account management with Kerberos and Active Directory

  1. Centralizing Accounts into ODSEE

The database establishes a connection to OUD. OUD retrieves user data (users and groups) from Oracle Directory Server Enterprise Edition (ODSEE) . EUS metadata are stored and retrieved from OUD.

This integration does not require any changes in the database (beyond what is usually required for EUS, nor for database clients that use username/password authentication.

eus_dsee[1]

Figure 4: EUS Account management with DSEE

  1. Centralizing Accounts into Novell eDirectory

The database establishes a connection to OUD. OUD retrieves user data (users and groups) from Novell eDirectory. EUS metadata are retrieved from OUD.

This integration does not require any changes in the database beyond what is usually required for EUS, nor for database clients that use username/password authentication.

Using Novell eDirectory doesn’t require an Oracle password filter. You have to enable Universal Password in eDirectory, and allow the administrator to retrieve the user password. Refer to Novell’s eDirectory documentation on Password Management for more information.

This configuration can only be used with DB versions 10.1 or higher due to incompatible password formats in earlier DB versions.

eus_edir[1]

Figure 5: EUS Account management with DSEE

OUD&EUS Take 1: DB Accounts Stored in OUD

By Sylvain Duloutre on Jul 09, 2013

This post is the first one of a serie focusing on Enterprise User Security (EUS) and Oracle Unified DIrectory (OUD).

Enterprise User Security (EUS), an Oracle Database Enterprise Edition feature, leverages the Oracle Directory Services and gives you the ability to centrally manage database users and role memberships in an LDAP directory. EUS reduces administration costs and increases security

Storing DB Accounts in OUD

OUD is specifically tailored to work seamlessly with EUS. Database user information, passwords and privileges information for a database or for a database domain can be stored in OUD.

EUS can leverage existing user and group information stored in OUD to provide single password authentication and consistent password policy across enterprise applications. User data, database meta-data, such as DB registration information, user/role Mappings, and other EUS specific meta-data are stored in OUD using a specific, supported, read-to-use LDAP schema. These meta-data are stored in a separate OUD suffix, called Oracle Context, making a clean logical separation between EUS data and user information that can be shared across applications.

In addition to providing centralized database user management, Enterprise EUS provides three different methods of user authentication: X.509 certificate authentication (introduced in DB 8i); Password-based authentication (since DB 9i); and authentication via Kerberos (since DB 10g). OUD support for Password-based authentication for EUS was introduced in OUD 11gR2. The other authentication methods were introduced in OUD 11gR2PS1.

In the password authentication scenario, the database does not perform user authentication via LDAP bind to OUD. Instead the database collects user credentials, hashes the password, and compares the password hash value retrieved from OUD. More detailed information about EUS can be found in the Enterprise User Administrator’s Guide in the Database documentation section on OTN.

eus_general[1]

Enabling EUS support in OUD 11gR2 using command line interface

Enterprise User Security (EUS) allows Oracle Database to use users & roles stored in LDAP for authentication and authorization.
Since the 11gR2 release, OUD natively supports EUS. EUS can be easily configured during OUD setup. ODSM (the graphical admin console) can also be used to enable EUS for a new suffix.

However, enabling EUS for a new suffix using command line interface is currently not documented, so here is the procedure:

Let’s assume that EUS support was enabled during initial setup.
Let’s o=example be the new suffix I want to use to store Enterprise users. The following sequence of command must be applied for each new suffix:

// Create a local database holding EUS context info
dsconfig create-workflow-element –set base-dn:cn=OracleContext,o=example –set enabled:true –type db-local-backend –element-name exampleContext -n
// Add a workflow element in the call path to generate on the fly attributes required by EUS
dsconfig create-workflow-element –set enabled:true –type eus-context –element-name eusContext –set next-workflow-element:exampleContext -n
// Add the context to a workflow for routing
dsconfig create-workflow –set base-dn:cn=OracleContext,o=example –set enabled:true –set workflow-element:eusContext –workflow-name exampleContext_workflow -n
//Add the new workflow to the appropriate network group
dsconfig set-network-group-prop –group-name network-group –add workflow:exampleContext_workflow -n

// Create the local database for o=example
dsconfig create-workflow-element –set base-dn:o=example –set enabled:true –type db-local-backend –element-name example -n

// Create a workflow element in the call path to the user data to generate on the fly attributes expected by EUS
dsconfig create-workflow-element –set enabled:true –set eus-realm:o=example –set next-workflow-element:example –type eus –element-name eusWfe
// Add the db to a workflow for routing
dsconfig create-workflow –set base-dn:o=example –set enabled:true –set workflow-element:eusWfe –workflow-name example_workflow -n
//Add the new workflow to the appropriate network group
dsconfig set-network-group-prop –group-name network-group –add workflow:example_workflow -n 

// Add the appropriate acis for EUS
dsconfig set-access-control-handler-prop \
–add global-aci:'(target=“ldap:///o=example”)(targetattr=”authpassword”)(version 3.0; acl “EUS reads authpassword”; allow (read,search,compare) userdn=“ldap:///??sub?(&(objectclass=orclservice)(objectclass=orcldbserver))”;)’
dsconfig set-access-control-handler-prop \
–add global-aci:'(target=“ldap:///o=example”)(targetattr=”orclaccountstatusevent”)(version 3.0; acl “EUS writes orclaccountstatusenabled”; allow (write) userdn=“ldap:///??sub?(&(objectclass=orclservice)(objectclass=orcldbserver))”;)’

Last but not least you must adapt the content of the ${OUD}/config/EUS/eusData.ldif  file with your suffix value then inport it into OUD.

Enabling support of EUS and Fusion Apps in OUD

Since the 11gR2 release, OUD supports Enterprise User Security (EUS) for database authentication and also Fusion Apps. I’ll plan to blog on that soon. Meanwhile, the R2 OUD graphical setup does not let you configure both EUS and FusionApps support at the same time.

INBOX)67103[1]

However, it can be done manually using the dsconfig command line. The simplest way to proceed is to select EUS from the setup tool, then manually add support for Fusion Apps using dsconfig using the commands below:

– create a FA workflow element with eusWfe as next element:
dsconfig create-workflow-element \
–set enabled:true \
–set next-workflow-element:Eus0 \
–type fa \
–element-name faWfe

– modify the workflow so that it starts from your FA workflow element instead of Eus:
dsconfig set-workflow-prop \
–workflow-name userRoot0 \
–set workflow-element:faWfe

Note: the configuration changes may slightly differ in case multiple databases/suffixes are configured on OUD.