While preparing to install OAM 11g, some of us were curious whether all the "ob..." attributes would remain intact or if they would be renamed with, for instance, an "orcl..." prefix. It struck one of my colleagues that the "ob" attributes would survive, if only to facilitate a workable upgrade path or to ease product development.
It is unlikely that many will have this problem, but if you do this could save some time and headache troubleshooting...
Upgrade from COREid 7 to OAM 10.1.4.0.1 process drops the root CA......
When using a older Access Server SDK (7.0.4) with a newer Access Server (10.1.4) running in backward compatibility mode recently,
When creating a custom style for Oracle Access Manager (formerly COREid) the product creates a localized directory for you in the default language, but all of the files in the localized copy point back to the main style sheets in the shared directory. In order to keep the vanilla sheets for style0 (Classic Style) intact it is advisable to create a duplicate shared directory (i.e. newstyle_shared).
A web server with a WebGate installed on it suddenly does not serve pages and generates 500 errors.
Successful migrations of Oracle Access Manager (formerly COREid) configuration data rely heavily on consistent directory naming of entries between envionments.
Successful migrations of Oracle Access Manager (formerly COREid) configuration data rely heavily on consistent directory naming of entries between envionments.
Nulli Secundus is pleased to announce that our COREid Migration Service has entered a pre-beta (invitation only) phase.
Have you ever wanted to get a nice clean schema file containing all of your custom attirbutes and object class entries but exluding the special microsofty attributes from and AD/AM (or AD) instance so that you can archive it off into a source control system or just simply migrate it to another environment?
Gettng quite specific here - but if you have this problem, you'll appreciate the info...
In COREid deployments where the Access and/or Identity services are installed on the same box as the LDAP server, the COREid service(s) sometimes start faster than LDAP.
A common request for COREid customization is removing unused menu options in the User Manager, Group Manager, and Org. Manager applications (like Create User Identity, Deactivated User Identities, Configuration, etc).
When simple mode certificates are going to expire, .......
Have you ever needed to bulk load AD/AM with a bunch of LDIF users for testing or conversion purposes, but been frustrated by its inability to allow password changes over an unsecured port?
Ever enabled the NetPoint Identity Domain policy domain but not NetPoint Access Manager?
By default Oracle COREid simple mode certificates are issued for 1 year (365 days) by default.
Some people look at the vanilla COREid interface and make a quick decision that they don't like it, or that it's not what they hoped it to be.
Have you ever got confused when using substitution syntax in COREid search base and attribute access control settings?
Ever wanted to reduce or increase the AD/AM search limit (page size)?
Have you ever had some header variables show up and not others?
OK, so COREid supports rudimentary pattern matching in policy patterns. For instance, one can create a URL pattern in a policy definition that matches multiple URLs with a single policy (pattern).
