The following issues were fixed in RSA Identity Governance and Lifecycle version 7.1.1 Patch 6.
Issue | Description |
---|---|
SF-1379553 ACM-98675 | Filtering on the Account User column in account reviews threw an IndexOutOfBound error when the accounts in review had changed from one of orphaned, single user, or shared to another during collections that occurred after the review is generated. |
SF-1443568 ACM-93656 | A role review could not be completed if the role had a parent, due to review generation incorrectly adding the parent role as a sub role. |
SF-1474519 ACM-102154 | When exceptional access granted from a violation review expired while the same review was still active, the violating entitlements were no longer excepted, and the remediator was unable to re-grant exceptional access. |
SF-1499829 ACM-102779 | Review monitors with read and write privileges on a review were incorrectly able to edit and create escalations on reviews. |
SF-1484596 ACM-102479 | Alternate managers were able to self-review items even when the self-review option was not enabled on a review. |
SF-1457499 ACM-101644 | Mandatory review comments did not always cascade to child entitlements. |
Issue | Description |
---|---|
SF-1499545 ACM-102679 | When multiple roles exist with the same raw name due to deleted roles, creating a change request for that role failed because the system selected a deleted role entry instead of the active entry. |
SF-1423357 ACM-100749 | In a change request, the role name is displayed inconsistently, at times using the role raw name. |
SF-1490087 ACM-102516 | Some Role Names were unexpectedly changed to Role Raw Names without a change request. |
Issue | Description |
---|---|
SF-1492500 ACM-103314 | The user interface previously allowed users to cancel change request items in a pending verification state only if the change request was in the open state and the workflows were in an active state. |
SF-1472575 ACM-103356 | Clarification was needed that the "Max items per change request" setting does not affect change requests that add or remove entitlements from roles. |
SF-1477172 ACM-102222 | Requests with all watches closed incorrectly remained open. |
SF-1461349 ACM-102856 | The change request milestone for completed manual activity incorrectly displayed a message that it was completed by the system. |
SF-1549667 ACM-103680 | When a pending account had dependencies in another change request, and the pending account's change request was rejected by the approver, all of the items other than the pending account were rejected, and the pending account was provisioned. |
Issue | Description |
---|---|
SF-1545433 ACM-103476 | The REST connector used returned set-cookie headers in subsequent calls, resulting in failed login attempts. |
SF-1488532 ACM-102526 | Could not clear the mysql-connector-java-5.1.36-bin.jar from a MySQL connector after it was loaded. |
SF-1545433 ACM-103475 | The REST connector was adding unnecessary, unconfigured HTTP headers to configured capabilities. |
SF-1545433 ACM-103474 | Improved security of REST connector parameters. |
Issue | Description |
---|---|
SF-1475181 ACM-102535 | Custom aliases used for the "Application backup technical owner" and "Business unit backup technical owner" attributes were switched in the Application page user interface. |
Issue | Description |
---|---|
SF-1485534 ACM-102501 | Stack overflow errors from queries were not caught and handled as expected. |
SF-1537490 ACM-103555 | Unification did not properly update the Terminated Flag for a user causing Termination Rule to not work properly. |
Issue | Description |
---|---|
SF-1513501 ACM-103057 | After upgrading the JDK, installing a patch failed with a "No such file or directory" error. |
Issue | Description |
---|---|
SF-1468644 ACM-103319 | A change request was unable to process the removal of a local entitlement from a deleted user. |
Issue | Description |
---|---|
SF-1483936 ACM-102582 | After running an unscheduled report, the related email incorrectly attached the last scheduled report. |
Issue | Description |
---|---|
SF-1510893 ACM-102974 | In a request form, the user picker field did not show the selected user value. |
Issue | Description |
---|---|
SF-1539132 ACM-103354 | Deleted or obsolete role versions were occasionally not properly removed from system tables. |
SF-1518077 ACM-103240 | Custom Attribute columns displayed an incorrect value during role analysis for suggested entitlements. |
SF-1485467 ACM-102423 | When exporting all roles, the entire export failed when an unexpected error occurred for any of the included roles. |
SF-1134364 ACM-86976 | The role management history table occasionally displayed two instances of the role to change request link instead of just one. |
SF-1547382 ACM-103544 | RSA Identity Governance and Lifecycle handled identical change requests differently when they were made for business roles or single entitlements. |
SF-1433180 ACM-100944 | The role entitlements screen for Direct Missing Members displayed incorrect users. |
Issue | Description |
---|---|
SF-1419233 ACM-100266 | Unable to change the status of a rule when the rule action to send email contained deleted users. |
SF-1470661 ACM-102053 | User coverage in Segregation of Duties (SoD) rules did not filter users with a null attribute value. |
SF-1452352 ACM-101601 | UINC rules were unexpectedly triggered, reassigning access to terminated users. Terminated users are now excluded from being assigned access. |
Issue | Description |
---|---|
SF-1440495 ACM-101268 | Grouping on the Requests > Requests page erroneously included change lists that were in the pending submission state, resulting in an error when a user expanded a grouping that included one or more pending submission change requests. Group queries now exclude partially submitted change requests. |