This chapter describes issues associated with Oracle Entitlements Server. It includes the following topics:
This section describes general issues and workarounds. It includes the following topics:
When using simple search in the Oracle Entitlements Server Administration Console to search for External Roles and Users of an Application bound to an Identity Directory Service profile, the search results for the Application Roles are incorrect. The issue occurs when the bound Application is not the first item in the Application drop-down list and you did not change the Application manually when you searched for Application Roles. To work around this issue, choose the application you want to search in drop-down box of simple search panel.
If you want to create an Identity Directory Service profile in an 11g Release 2 (11.1.2.3) environment that had been upgraded from 11g Release 2 (11.1.2.1), you must create the new IDS profile in the Oracle Entitlements Server Administration Console, and in the User section, enter uid in the Global Common ID Attribute field.
In 11g Release 2 PS1, the Global Common ID Attribute field did not exist. In 11g Release 2 (11.1.2.3) the Global Common ID Attribute value is required. If you do not enter a value in this field, an error message results when you try to create the Identity Directory Service profile.
This section describes configuration issues and their workarounds. It includes the following topics:
When saving the identity/trust store password into the credential store, the ./oesPassword.sh –initenroll command fails for Security Modules in controlled-push mode that use a third party digital certificate. The following error occurs:
oracle.security.jps.service.policystore.PolicyStoreException: oracle.security.jps.service.policystore.PolicyStoreException: java.security.UnrecoverableKeyException: Password must not be null
To work around this issue, you must run./oesPassword.sh –initenroll again to successfully save the password into the credential store.
The WCC-OES Connector fails to install during Oracle WebCenter Content and Oracle Entitlements Server integration. To work around this issue, you must perform the following steps before installing the WCC-OES Connector ("Installing the WCC-OES Connector" in Administering Oracle Entitlements Server):
Back up $OESCLIENT_HOME/oessm/ucmconnector/components/UCM_OES_Environment.cfg.
Update UCM_OES_Environment.cfg to:
<?cfg jcharset="UTF8" encoding="UTF-8"?> applicationName=UCM Application crudResourceType=UCM CRUD Operation Resource Type searchResourceType=UCM Pre-Search Query Resource Type
Copy it to the folder $wcc_domain/ucm/cs/custom/UCMOESConnector/.
The PD Client is deployed to the Managed Servers by default if you choose the Oracle Entitlement Server Weblogic Security Module template and configure the Managed Server for the domain when you run config.sh.
To work around this issue, when you run config.sh (located in OES_CLIENT_HOME/oessm/bin), in the Target Deployments to Clusters or Servers page, click AdminServer, and then, choose the application oracle.oes.client.pd.ssl#11.1.1.3.0 so that the PD Client is deployed to the Administration Server. You can also unchecked the Managed Servers from the target servers.
This section describes documentation errata for Oracle Entitlements Server-specific manuals. It includes the following titles:
There are no issues to document for Administering Oracle Entitlements Server.
There are no issues to document for Developer's Guide for Oracle Entitlements Server.