Will the LDAP Scripts Provided for OID from Bug 14101542 Cause More Harm than Good? (Doc ID 1666461.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Access Manager - Version 11.1.2.1.0 and later
Information in this document applies to any platform.

Symptoms

Will be updating environment to correct the problem described in:
<Note:1496808.1> - Automatic Locking and Unlocking of the Users in OAM Integrated OIM Environment
<Bug:14101542> - oim not compatible with oam 11g oblockouttime (orcluserlockedon) attribute

Specifically step 3:

Step 3:
--------
The OAM (Oblix) LDAP schema must be extended with the obLockeOn attribute changes. For details refer to the

$ORACLE_HOME/oam/server/oim-intg/ldif//schema/*

files after the required OAM patch has been installed. Please note that for OUD the is ojd.


The note states to run the ldif scripts in this directory
$ORACLE_HOME/oam/server/oim-intg/ldif/oid/

The OID_oblix_schema_index_add.ldif:1, re-indexes ALL of the indexed directory attributes

Oracle® Fusion Middleware Administrator's Guide for Oracle Internet Directory  11g Release 1 (11.1.1)  Part Number E10029-03
20.3.7 Indexing an Attribute for Which No Data Exists by Using ldapmodify


This document states ...

After you define a new attribute in the schema, you can add it to the catalog entry by using ldapmodify.

To add an attribute for which no directory data exists, import an LDIF file by using ldapmodify. For example, to add a new attribute foo that has already been defined in the schema, import the following LDIF file by using ldapmodify:
dn: cn=catalogs
changetype: modify
add: orclindexedattribute
orclindexedattribute: foo


Type a command similar to the following at the system prompt:
ldapmodify -D "cn=orcladmin" -q -h host -p port -f ldif_file_name


* You should not use this method to index an attribute for which data exists in the directory. To index such an attribute, use the Catalog Management tool, catalog.  See "15.7 Creating and Dropping Indexes from Existing Attributes by Using catalog".


Based on the collected information will the LDAP scripts provided for OID from Bug 14101542 cause more harm than good?

Cause

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