It includes the following topics:
This section describes general issues and workarounds. It includes the following topics:
There are multiple JMX and DMS related warnings during server startup and one error with following message when accessing oaam_admin for the first time:
[2013-02-08T12:07:47.402-08:00] [oaam_admin_server1] [ERROR] [WCS-16178] [oracle.adfinternal.view.page.editor.utils.ReflectionUtility] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: MATSruleadmin] [ecid: 0000JmvQtubBP9W5Hz5Eif1H5LY800001M,0] [APP: oaam_admin#188.8.131.52.0] Error instantiating class - oracle.adfdtinternal.view.faces.portlet.PortletDefinitionDTFactory
This section describes Session Details page issues and limitations. It includes the following topic:
The Session Details page has no scrollbars which may prevent you from viewing the Alerts summary in the Checkpoint details panel. There is also unused space between the collapsed Session Details and Checkpoints panels.
In the Alert section of Checkpoint Details in the Session Details page, the "High" and "Medium" color coded alerts do not meet the minimum color contrast ratio of 4.5:1.
"High" text contrast is 4.0:1.
"Medium" text contrast is 1.97:1.
To work around this issue, enable High Contrast mode in Windows and OAAM.
In the Session Details page, the following tables have filters:
Checkpoints results table
Transactions results table
The filters along with the real column header are listed as column headers; as a result, the screen reader (JAWS) reads both when traversing through a table which may cause confusion. This is a known issue, and a workaround is currently not available.
In the Session Details Transaction and Checkpoint panels, the selection radio buttons are labeled "Select Row 1" instead of something more meaningful to the user, e.g., "Select row 1 Checkpoint_name" in the Checkpoint panel or "Select row 1 Transaction id Transaction_id" for the Transaction panel. Currently, the user must traverse the table to know the kind of data he is selecting.
In the Session Details page transactions data table, the transaction data summary tree is labeled "tree table" instead of something more meaningful to the user, e.g., "Transaction Data."
This section describes issues and limitations related to Agent cases. It includes the following topic:
When replacing an Agent case with another Agent case, you may see the following pop-up window:
Transaction type cannot be null or empty
The error message appears when there are no transaction definitions in the system, and you try to replace an Agent case with another Agent case. Currently, you are required to configure at least one transaction definition. The pop-up window does not appear if the system has at least one transaction definition. To work around this issue, configure at least one transaction definition. The problem will be fixed in an upcoming release.
In the OAAM Administration Console, the Agent Cases tab is completely blank when signed in as an Investigator or Investigation Manager. The Cases Search page should be displayed along with the search filters and search result table.
As a workaround, perform the following steps:
From the Agent Cases tab, click another tab to change the focus. For example, you can click the Sessions or Search Transactions tab.
Then, click the Agent Cases tab to change the focus back.
Now the Agent Cases tab displays the Agent Cases page and all the functionality work properly.
When logged in as an Investigator or Investigation Manager (user is a member of the OAAMInvestigatorGroup or the OAAMInvestigationManagerGroup role), after using the browser refresh, some actions in the application do not have effect until a browser refresh is performed again. Each action requires a browser refresh until a new session is started.
This section describes multi-language support issues and limitations. It includes the following topics:
Searching for a KBA question using Category with Locale filters does not work. For example:
On a browser set for English, if the user searches with "Parejo" as the category and "Spanish" as the locale, the search results display KBA questions, but the category is shown as "Significant Other." The correct locale is not displayed.
On a browser set for Spanish, the search results display Spanish KBA questions with "Parejo" as the category but the locale is shown as English. If the user searches by the combination of "Parejo" and "Espanol," the search results display no records.
In some areas of the OAAM Administration Console, the double apostrophe is displayed where a single apostrophe should be when the browser language is set to French. The areas include:
Tooltips on the Job queue page
Import operation was successful message
Tooltip in the Jobs page, such as Activer l''élément travaux sélectionné
Tooltip in Open Selected from Action menu in all pages
Policy - Group Linking tab, such as L''ajout de lien de groupe ne s''applique pas...
Policy Set - Action Override tab
Policy page error messages
Session page error messages
User summary - Profile data section, such as Groupes d''utilisateurs
Entities page text, such as Utilisez l''outil de recherche pour rechercher un...
This section contains documentation errata for the following document:
Oracle Fusion Middleware Java API Reference for Oracle Adaptive Access Manager does not provide information about the status values for
setUserStatus. Valid status values are as follows:
public static final int STATUS_PENDING_ACTIVATION = 1; public static final int STATUS_ACTIVE = 2; public static final int STATUS_DISABLED = 3; public static final int STATUS_DELETED = 4;
The user started registration, but has not completed it. He has entered his username and password and his information has been stored in the database, but he will not be activated until he has completed registration. The user is available in the system, but he is not yet active and cannot perform any operations.
The user is active and available in the system. He has completed registration and can perform all operations.
The user is available in the system, but not active. He may be disabled because of fraud or other reasons and cannot perform any operations.
The user is not available in the system.