The following issues were fixed in RSA Identity Governance and Lifecycle version 7.1.1 Patch 4.
Issue | Description |
---|---|
SF-1451847 ACM-101388 | Coverage files were erroneously not applied to review items associated with deleted objects. |
SF-1385200 ACM-98887 | Inefficient SQL statements were called with every move through the tabs of the Role screen. |
SF-1355180 ACM-98148 | The EmailByMonitor message type did not consider the configured columns in the review. Instead, it had only considered the hard-coded columns. |
SF-1372625 ACM-97914 | When performing review analysis, the ORA-30926 error could be generated when calculating unchanged review items because of the incorrect join that compared old review items to items in the current review. |
SF-1398246 ACM-98991 | Refreshing any review data other than business descriptions resulted in coverage information automatically refreshing, even when the option to refresh coverage was not selected. |
SF-1383316 ACM-98384 | Account reviews that filtered accounts and groups could experience poor performance during review generation. |
Issue | Description |
---|---|
SF-1373606 ACM-99457 | Duplicate accounts were created when a pending account was created with the same name but different capitalization as another account in a case-insensitive ADC. The next time the accounts were collected for the case-insensitive ADC, the pending account’s name is updated to match the capitalization, which caused duplicate accounts in the system. The system will now take an ADC's case-sensitivity into consideration and result in an error when necessary. |
SF-1354678 ACM-97131 | Account creation change requests could fail when the account parameter was mapped with attributes of more than one type, because the code failed to group them based on the type. |
Issue | Description |
---|---|
SF-1300643 ACM-94655 | On a request form, when a form field was mapped to a provisioning parameter that contained encrypted values, the form did not properly substitute the correct value when generating the request. |
Issue | Description |
---|---|
SF-1329501 ACM-95778 | When multiple SSO User Headers authentication sources were configured, an authentication source was randomly picked without verifying the authentication source name during authentication. |
Issue | Description |
---|---|
SF-1426513 ACM-100295 | In a workflow that is configured to group by business source, password resets skipped the workflow and the change request workflow completed with the item still in Pending Action status. |
SF-1461377 ACM-101694 | An access request generated thousands of unrelated activities when a call to filter change request items for a subprocess returned an empty list. Now, if this occurs, an exception occurs and an error message is displayed for user interface operations. For operations that are not performed through the UI, the processing will go to the Error state. |
SF-1445481 ACM-101508 | A pending change item with the type Container was erroneously displayed in the User Changes table. |
SF-1436645 ACM-100872 | A user could submit a change request with a pending submission from the Additional Information submission screen. This fix disables the Finish and Next buttons in this use case. |
SF-1429237 ACM-100448 | Admin > Workflow > Monitoring did not update the Pending Verification (Count) icon when the number of pending verification items changed. |
SF-1211444 ACM-89746 | The Workflow Architect failed to load when using SSO because the double slash // in the URL caused issues with some web agents. |
SF-1302839 ACM-96673 | Could not open workflows because the URL contained a double slash //. |
SF-1344121 ACM-97053 | Variables were not populated in emails for account review change requests when revoking an account from a group. |
SF-1391209 ACM-98951 | In the out-of-the-box Reassign to Supervisor node, the Comments field was missing from the Resource sections. |
Issue | Description |
---|---|
SF-1437194 ACM-101006 | An account collector had performance issues when searching for a cycle of groups in an environment with multiple ADCs when one ADC collected the majority of groups but the SQL explain plan was not appropriate for that collector. |
SF-1348150 ACM-94653 | Updated the driver that does SQL processing of the CSV files involved in collections. This address bug fixes in the driver on earlier versions. |
SF-1453582 ACM-101456 | After modifying a collector, the Last Modified value was not updated. |
SF-1437248 ACM-100836 | The Archer account data collector switched the values for email and phone numbers in collected data. |
Issue | Description |
---|---|
SF-1276541 ACM-92962 | When editing an object on which a managed custom date attribute was previously set, the attribute field was blank. |
SF-1414773 ACM-99715 | The field length of custom attributes did not match the field length in the base tables. |
Issue | Description |
---|---|
SF-1405466 ACM-99282 | Inactivating an IDC that creates users and moves a subset of users to another collector creating users could cause duplicates in the next Unification run. |
SF-1469467 ACM-101996 | When a user record was terminated during an IDC full refresh, a duplicate identity record could be created during a user rehire scenario. |
Issue | Description |
---|---|
SF-1403444 ACM-99867 | When database purging exceeded the threshold of four hours, the process did not exit and complete as expected. |
SF-1441958 ACM-100974 | During archive creation, the archive start date was calculated incorrectly resulting in the following error: "The archive Start and End dates can not be overlapping with the existing archives." |
SF-1437637 ACM-100899 | After deleting archive runs from the monitoring page, the runs were deleted from the system and an error was displayed when trying to view the archive table. |
SF-1292988 ACM-94898 | Performance problems could occur while accessing the raw data for a collection when there was a large amount of rejected data in the tab being accessed. |
Issue | Description |
---|---|
SF-1235688 ACM-92268 | During virtual application installation, the following error could occur in environments with a customer-supplied database: “[Step 1 of 9] Error configuring certificates ('./configureSSLCertificates.sh')”. |
Issue | Description |
---|---|
SF-1408780 ACM-99393 | All items on the metadata export screen were erroneously selected when browsing between pages. |
Issue | Description |
---|---|
SF-1406053 ACM-101119 | Upgrading to a patch failed due to increased security restrictions on the "DUAL" table when it was used by Views. RSA Identity Governance and Lifecycle has now deprecated the use of this table in views. |
SF-1419230 ACM-100075 | Migration from 6.9.1 failed due to locked statistics on some tables. |
Issue | Description |
---|---|
SF-1407060 ACM-99468 | A Java exception was displayed on the Expiring Passwords tab when displayed a user account’s expiring password details. |
Issue | Description |
---|---|
SF-1445499 ACM-101319 | ASR report generation failed when the Environment Name was 100 characters of longer. |
SF-1406193 ACM-100547 | Reports did not display line breaks in the Long Description attribute of entitlements. |
SF-1347793 ACM-97050 | After specifying an equals filter for an application name, its alternate name was saved in the report XML while the underlying view contained the raw name. Because of this mismatch, the report did not generate results or load the filter properly when the report was reopened. This also occurred with other objects that had alternate names. The system now saves the raw name as expected to prevent this issue. |
SF-1405003 ACM-99240 | ASR report generation failed with an ORA-06502 error when an environment name exceeded a length of 100 characters. |
Issue | Description |
---|---|
SF-1356824 ACM-98731 | Request forms that used additional filters were not isolated from the main query, which caused the user counts to be incorrect. |
SF-1401041 ACM-99601 | Unable to create an out-of-office request when additional fields under Requests > Configuration > Submission were present but not enabled for display. |
SF-1442831 ACM-101157 | When a JSP file was referenced in the Validation URI for a request form, an exception occurred. |
SF-1429864 ACM-100556 | After performing an upgrade, an error occurred loading the fields in a request form that had previously worked. |
Issue | Description |
---|---|
SF-1434279 ACM-100697 | Change items were missing from a change request after roles with varying levels of indirect group entitlements where removed from users. |
SF-1460209 ACM-101676 | Role export failed with error ORA-12899 when role names exceeded 128 characters. |
Issue | Description |
---|---|
SF-1345900 ACM-98473 | When entitlements of different types had the same ID, suggested entitlements could include empty or invalid entitlements. The query has now been fixed to join on entitlement type as well as ID. |
SF-1394356 ACM-98992 | Testing a rule took significantly longer to display the results than the time the actual rule run took to generate violations. |
Issue | Description |
---|---|
SF-1213280 ACM-98087 | Improved security of X-Content-Type-Options headers in responses from RSA Identity Governance and Lifecycle. |
SF-1213280 ACM-98085 | Improved security surrounding the session token for requests to Identity Governance and Lifecycle. |
Issue | Description |
---|---|
SF-1272396 ACM-92729 | The Wildfly application server log was not updating as expected after upgrading. |
SF-1463337 ACM-101994 | Data archiving failed with the ORA-06512 error. |
Issue | Description |
---|---|
SF-1446680 ACM-101222 | When viewing User > Requests or collection run details from the Collector History tab of a specific collector, the displayed breadcrumbs were incorrect. |
SF-1402236 ACM-99526 | When adding entitlements to a role, if the “one of” filter was used, the ORA-00904: “ENTITLEMENT_NAME”: invalid identifier error occurred. |
SF-1460981 ACM-101695 | After upgrading, the Business Source column was missing from the accounts table under the ADC collector. This column has now been added back to the accounts table. |
SF-1374347 ACM-98126 | Loading the Review Definitions table took an excessive amount of time due to unnecessary fetching of reviewer/monitor coverage data that is not required to render the table. |
SF-1220192 ACM-90208 | Pop-up windows appeared outside of the viewable area of a user’s screen when the screen had scrollable content. |