This chapter describes issues associated with Oracle Adaptive Access Manager.
It includes the following topics:
This section describes OAAM Admin issues and workarounds. It includes the following topics:
This section describes session detail issues and workarounds.
Searching by "User Friendly Name" Does Not Return Any Results If Device Is Secure
In the Device tab of the User Details and Devices Details pages, searching by User Friendly Name does not return any results if the device is secure (Registered is true).
Searching by "Any Device" as the Device Type Does Not Return Any Results
In the Device tab of the Details pages (for example, User Details: Devices tab, Fingerprint Details: Devices tab, or Alert Details: Device tab) searching by Any Device as the Device Type does not return any results even when there are devices.
Searching by "null" as the User Friendly Name Returns All Results
In the Device tab of the User Details and Devices Details pages, searching by User Friendly Name with the value of null returns all results. The search should return only devices with the name null.
In the Device tab of the Session Details pages, sorting by Last Used On Dates does not work. The devices remain sorted by the Device ID as default.
Fingerprint Data Shows Incorrect Number of Fingerprints in the Session in the User Details Page
In the Profile Data section of the User Details page, the number of fingerprints in the session is shown as 0 in Fingerprint Data even when fingerprint data for the session is available and can be displayed in the Fingerprint Data tab.
When Multiple Transactions Are Created the Policy Data Becomes Out of Sync
If multiple transactions are created in a session and corresponding pre- and post-transaction policies are executed, the policy data in the Session Details page becomes out of sync. For example, if in the same session, there were 5 transactions which triggered different rules that in turn generated different types of alerts, the session details page data is not displayed correctly in the corresponding checkpoints.
Checkpoint and Transaction ID Selection Options Do Not Indicate the Data to be Selected
In the Session Details Transaction and Checkpoint panels, the selection buttons are labeled Select Row 1 instead of more meaningful labels to the user. For example, the labels could be 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.
Checkpoint and Transaction Filters Included as Table Column Headers
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.
Scrollbar Is Missing from Session Details Page When Screen Resolution is Low
The Session Details page does not display scrollbars which may prevent you from viewing the Alerts summary in the Checkpoint details panel.
High and Medium Alert Level Colors Do Not Meet Minimum Color Contrast Ratio
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.
The High text contrast is 4.0:1.
The Medium text contrast is 1.97:1.
To work around this issue, enable High Contrast mode in Windows and OAAM.
Bulk edit for closing CSR cases displays dispositions related to Agent cases.
This section describes OAAM Command Line Tool (CLI) issues and workarounds. It includes the following topic:
When running the OAAM command line tool (CLI), you cannot use a file-based CSF (oaam.csf.useMBeans is set to False). CLI cannot retrieve the credentials required to run the CLI scripts from the CSF and an access control exception is shown.
This is a known issue, and the workaround for this issue is to run CLI using a repository-based CSF with MBeans (oaam.csf.useMBeans is set to True).
For details about CSF with MBeans, see "Configure OAAM Database Details with CSF with MBeans" in Oracle Fusion Middleware Administrator's Guide for Oracle Adaptive Access Manager.
This section describes multi-language support issues and limitations. It includes the following topics:
The OAAM Admin Console may contain garbled characters when supplementary characters are used.
This section describes issues associated with multi-language support in KBA.
Duplicate Entries in the List of Categories
The Category drop-down list in the New Questions page may display multiple entries of the same categories in different languages.
Category Names are Displayed in English Irrespective of How the Category Name Was Entered in the Filter
If the browser language is set to English, the search results in the Question search page display the category name in English irrespective of the language you entered the category name in.
Unable to Search KBA Question by Category in Different Locale
When searching for KBA questions in the OAAM Admin Console, the Category and Locale filters do not work when used together. Examples are as follows:
In 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.
In 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.
This section describes T2P issues and limitations. It includes the following topic:
During the OAAM plug-in paste configuration operation if the OAAM domain does not exist, the paste configuration steps are skipped and the following message is displayed:
Not valid OAAM Domain. Skipping OAAM-specific copy configuration steps.
copy configuration steps should be changed to paste configuration steps.
This section describes API issues and limitations. It includes the following topics:
Section 7.5.1, "setUserDevices API Does Not Work Correctly in Some Cases"
Section 7.5.2, "getUserDevices API Returns Success Status for Invalid User ID"
setUserDevices API Does Not Work When Certain Inputs are Null
setUserDevices does not work correctly when certain inputs are null. The issues are as follows:
When an element in the UserDevice array is null but the rest are valid elements, setUserDevices returns an unexpected error and none of the devices are updated.
When the Device Map ID is null in the UserDevice object, setUserDevices returns a status of Success and the other valid devices are updated.
setUserDevices API Returns An Empty List When User Friendly Name Contains Special Characters
setUserDevices returns a null object when the User Friendly Name contains special characters.
getUserDevices returns a status of Success for an invalid user ID.
There is no documentation errata at this time.