Will the LDAP Scripts Provided for OID from Bug 14101542 Cause More Harm than Good?
Last updated on MARCH 08, 2017
Applies to:Oracle Access Manager - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
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:
The OAM (Oblix) LDAP schema must be extended with the obLockeOn attribute changes. For details refer to the
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
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 ...
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:
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?
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