The following issues were fixed in RSA Identity Governance and Lifecycle version 7.1 Patch 7.
Issue | Description |
---|---|
ACM-96153 SF-1332517 | After the scheduled run time for a review was changed, the task was duplicated in the memory and the review was run multiple times. |
SF-1273418 ACM-93625 | In the legacy user access review definition, previously selected options for the Replace state were reset when editing the review definition without opening the States tab. |
ACM-92635 | During delegation from the "By Reviewer" tab of reviews, a "Delegated From" user was incorrectly identified as the last reviewer when expanding the tab instead of the actual reviewer from whom items were delegated. |
SF-1159200 ACM-86631 | When a review item that had been maintained with expiration was revoked, the reviewer was incorrectly set to AveksaAdmin. |
SF-1159011 ACM-86618 | The status for a review was not updated properly upon review completion. |
SF-726389, ACM-61543 | In review definitions, the "include sub-groups" option was available for selection when no specific groups were selected. |
SF-1215725 ACM-90109 | Review generation took more than sixty hours when the review did not use the option “Include group memberships that are entitlements of their assigned global roles.” |
SF-1261298 ACM-94057 | When a role containing app-roles was deleted in a role review, change items to remove the app-roles were not generated. |
SF-1274991 ACM-92885 | The user interface took a long time to load certain tabs in reviews that had large data sets. |
SF-1215357 ACM-89832 | Users were able to schedule reviews and collectors using a past date. |
SF-1325510 ACM-95533 | Multi-step review generation failed when secondary step definitions enabled the user selection option "By selecting supervisors and using their subordinate users.” |
SF-1292722 ACM-94322 | A review with a value for SIGN_OFF_ENABLED other than Y or N caused a server startup failure. |
SF-968449 ACM-76811 | In a review definition that already had a coverage file that determined the monitors, if the definition was edited to deselect the coverage file option, the earlier coverage file was still saved with the review definition despite being displayed as unselected in the user interface. |
SF-1170215 ACM-87978 | When multiple users were selected, submission variables appeared in only the first change request. |
Issue | Description |
---|---|
SF-1170215, ACM-87978 | When multiple users were selected, submission variables appeared in only the first change request. |
SF-1299740 ACM-94324 | Change requests to remove a user from a group that were generated by a Group review did not complete if the fulfillment workflow was configured to “Create a Job per group.” |
SF-1264368 ACM-93112 | Optimized statements for Change Requests involved with determining missing or extra indirect entitlements. |
SF-964505 ACM-74785 | When a user is granted the same entitlement through both a role and an account and the account is deleted from the user, an error occurs when the role is later deleted from the user. |
SF-1316456 ACM-96218 | Pre-processing for unauthorized change detection failed with the ORA-06402: PL/SQL: numeric or value error. |
SF-1304787 ACM-94669 | Under Requests > Requests, clicking certain change requests resulted in the following error: “The request could not be handled” due to a bug in the Oracle JDBC driver. |
SF-1343435 ACM-96760 | Subject of email incorrectly contained HTML markup. |
SF-1290843 ACM-94916 | When canceling a change request there was a significant delay. |
Issue | Description |
---|---|
SF-1224247 ACM-90477 | Account information on the MAEDC wizard was not displayed as expected to users authorized to edit or administer the MAEDC. |
Issue | Description |
---|---|
SF-1191999 ACM-93039 | Output parameters were not resolved when DN suffix mapping was used for account creation. |
SF-1297770 ACM-94271 | When the database suddenly went down or was unable to connect to AFX, AFX stopped running until the AFX service was restarted. |
SF-1169677 ACM-87391 | In a clustered environment, afx start incorrectly checked for the application running in standalone mode. |
SF-1240999 ACM-91585 | Improved error messages with regards to connector configuration. |
Issue | Description |
---|---|
SF-1195900 ACM-91400 | Active Directory users were unable to authenticate from the host controller in a WildFly cluster environment. |
Issue | Description |
---|---|
SF-1314265 ACM-95190 | The Activities page loaded slowly when using a monitoring policy with a large number of activities and when filtering activities with the “By Entitlement” tab. |
SF-1275666 ACM-95849 | The workflow setting "Show job level variables" did not work as expected. |
SF-1293434 ACM-95053 | In a fulfillment workflow, REST nodes did not display job variables as expected. |
SF-1311025 ACM-94899 | A change request was canceled when an approver approved an indirect role that was deleted. |
Issue | Description |
---|---|
SF-1269198 ACM-92669 | After viewing a collector schedule without making changes, the system updated the Date Modified field of the Collector History with the time the schedule was viewed. |
SF-1357468 ACM-97660 | Airwatch ADC Collector tests failed with an API end-of-life error. |
SF-1131553 ACM-85344 | The Salesforce Entitlement Data Collector on versions 7.0.0 or 7.0.2 failed when collecting large data sets. |
SF-1262200 ACM-92309 | The account data collector incorrectly processed the AD PwdLastSet attribute when the value was set to zero. |
SF-1196283 ACM-90783 | Data on the account/entitlement collector page loaded more slowly than expected. |
Issue | Description |
---|---|
SF-1187149 ACM-88462 | Custom user attributes were not populated in the table options of the accounts tab. |
SF-1295911 ACM-94081 | After setting a specific user as a Backup Business Owner or Backup Technical Owner for any Directory, Application or Role set, when the user's name was changed through the IDC, the CAU1_NAME attribute was not updated and the application object showed an outdated name in details, tables, and pop-ups. |
Issue | Description |
---|---|
SF-1156786 ACM-88676 | An object dashboard was not displayed in the order expected based on the specified Display Sequence value. |
SF-769669 ACM-60805 | A dashboard using the component System Portlet: System Summary displayed incorrect values. |
Issue | Description |
---|---|
SF-1314874 ACM-95225 | Objects in relationships that were deleted and revived in prior collections caused changed relationships to be rejected during collection. |
Issue | Description |
---|---|
SF-1280916 ACM-94602 | When running the data archiving function, the data archiving process completed as expected but the purging process fails due ORA errors. |
SF-1390655 ACM-98805 | Data purging failed with error ORA-02292. |
Issue | Description |
---|---|
SF-1293405 ACM-95236 | Special characters were not displayed properly in email subjects. |
Issue | Description |
---|---|
SF-922041 ACM-78015 | Patch installation took an unusually long time to complete. |
Issue | Description |
---|---|
SF-1341401 ACM-96645 | Deprecated migrate_deleted_connectors code because it was failing during role migration. |
Issue | Description |
---|---|
SF-1219878 ACM-90513 | A new public view was needed for a customer’s reporting purposes. |
Issue | Description |
---|---|
SF-1224614 ACM-91417 | The error message “An error occurred loading the fields for the form” occurred when running a form if the “Hide table if empty” option was enabled for an entitlement table that contained a dynamic value. |
SF-1348816 ACM-96918 | Checkboxes on a form were not disabled when the form was disabled. |
SF-1361380 ACM-97592 | Users were unable to submit a form that used an external validation URI, because the Next button was unusable. |
SF-1278644 ACM-96541 | Request forms allowed the selection of entitlements for a user that they had already been indirectly granted. |
Issue | Description |
---|---|
SF-1156540 ACM-87243 | An invalid Outstanding Requests page appeared after attempting to add entitlements from a user’s role. |
SF-1331149 ACM-95790 | During role creation, users who were configured as the Other Technical Owner for some role sets and who had the Role Set: View All entitlement were erroneously able to create roles under any role set. |
SF-1331250 ACM-95788 | The Role Creation wizard displayed a role set’s raw name instead of the role set name to technical and business owners. |
SF-1332139 ACM-96219 | A role membership rule could not be removed or deleted after it was created. |
SF-1377952 ACM-98164 | When the Apply Changes button was clicked on a changed global role, the View Changes link incorrectly showed the same entitlements as both added and removed. |
SF-1208476 ACM-91790 | Under rare circumstances, Aveksa Entitlements became out of sync when the privileges were granted or revoked through a Role or a Group. |
Issue | Description |
---|---|
SF-1333143 ACM-95904 | A provisioning/termination rule did not create change requests to revoke entitlements when there are accounts to disable and delete. |
Issue | Description |
---|---|
SF-1158051 ACM-87527 | Additional validation was required for JSP files uploaded in the Admin section. |
Issue | Description |
---|---|
SF-673708 ACM-53828 | Under Resources > Applications, in the Accounts tab, custom attributes were not displayed for Application Roles or Entitlements. |
SF-1246951 ACM-91654 | Intermittent high CPU usage caused performance issues in the RSA Identity Governance and Lifecycle user interface. |
SF-1048792 ACM-81142 | Under Reviews > Activities, when an Actions menu appeared at the bottom of the page, some menu options were cropped out of view. |
SF-1324961 ACM-95538 | Users granted view access to a group's directory could not see the group members. |
SF-1301016 ACM-94283 | In the list of applications, the Sensitivity column was not available in the table options under Displayed Columns. |
SF-1330310 ACM-95789 | A custom help URL did not work immediately after logging into RSA Identity Governance and Lifecycle. |
Issue | Description |
---|---|
SF-1319168 ACM-95505 | Change requests created from a web service erroneously included a deleted account. |