RSA^® Governance & Lifecycle

Article Number 000069903 Applies To This is a known issue in the following version: RSA Governance & Lifecycle 8.0.0 Issue When creating a new Provisioning Command node (or editing an existing one) if any of the attribute mapping Names are not assigned a Value then when the workflow is saved, the list is saved incorrectly.  Items that have null values in the list are not saved and the values from the names lower in the list are saved instead (moved up). Image description This can cause a variety of unexpected failures.     Cause The WorkPoint editor does not correctly save null values. Resolution This issue is resolved in the following version: RSA Governance & Lifecycle 8.0.0 P01 Workaround Contact RSA Customer Support if you cannot patch to the version where this is resolved.   ... View more

Article Number 000069902 Applies To This is a known issue with the migration of some connectors after upgrading from an older version to the following version: RSA Governance & Lifecycle 8.0.0 Issue Some AFX Connectors may show as "Not Deployed" in the Connectors page. Cause There is a race condition during copying of the archetype.jar when multiple 7.5.2 or earlier AFX connectors are queued for migration to 8.0.0 at the same time that causes some or all of the migrations to fail. Resolution This issue is resolved in the following version: RSA Governance & Lifecycle 8.0.0 P01 Workaround Contact RSA Customer Support if you cannot patch to the version where this is resolved.   Notes   ... View more

Article Number 000069281 Applies To This is a known issue in the following version: RSA Governance & Lifecycle 8.0.0 Issue The following AFX Connectors are affected: Active Directory OpenLDAP AFX provisioning fails for the following capabilities: Create an Account Update an Account Create a Group Update a Group The following is displayed on the UI when testing the connector: Error code = -1 CreateAccount failed due to following error: [LDAP: error code 21 - 00000057: LdapErr: DSID-0C090CB7, comment: Error in attribute conversion operation, data 0, v1db1] Cause: javax.naming.directory.InvalidAttributeValueException: [LDAP: error code 21 - 00000057: LdapErr: DSID-0C090CB7, comment: Error in attribute conversion operation, data 0, v1db1]; remaining name 'CN=Test5,OU=vcloud Users,DC=2k8r2-vcloud,DC=local' The following is logged in the esb.AFX-CONN-{connector name}.log: ERROR 2023-11-17 09:41:11,278 [[MuleRuntime].uber.141: [AFX-CONN-Active_DirectoryConnector].ldapFlow.BLOCKING @af25502] [processor: ldapFlow/processors/39/route/3/processors/5/route/0/processors/0/route/0/processors/0; event: 598213d0-8557-11ee-8f2c-0050560141b3] LdapOperationsImpl: Exception in UpdateAccount the error is as follows :[LDAP: error code 21 - 00000057: LdapErr: DSID-0C090C03, comment: Error in attribute conversion operation, data 0, v1db1]   Cause This issue occurs if there are some AFX optional attributes that do not have values ("[No value provided]"). Resolution This issue is resolved in the following version: RSA Governance & Lifecycle 8.0.0 P01 Workaround Contact RSA Customer Support if you cannot patch to the version where this is resolved.   ... View more

Article Number 000069907 Applies To RSA Product Set: RSA Governance & Lifecycle RSA Version/Condition:   SecurID Governance & Lifecycle 7.5.2 RSA  Governance & Lifecycle 8.0.0 Issue Stdout.log is not available in the log artifacts zip file. Image description Resolution This issue is resolved in the following versions/patches: RSA Governance & Lifecycle 8.0.0 P02 ... View more

Article Number 000069280 Applies To RSA Product Set: RSA Governance & Lifecycle RSA Version/Condition:  RSA Governance & Lifecycle 7.5.2 RSA Governance & Lifecycle 8.0 Issue The Role Raw Name is shown in the change request approval task instead of the role Display name. Image description Image description Resolution This issue is resolved in the following versions.  The solution requires being on the fixed version of the product AND configuring a custom parameter showRoleDisplayNameInChangeRequests. RSA Governance & Lifecycle 8.0 P02 To resolve the issue, first apply the fixed patch/version and then configure the custom parameter showRoleDisplayNameInChangeRequests as follows: On the UI, go to Admin > System > Settings > click Edit Scroll down to the bottom of the page, and add the following custom parameter: Parameter name = showRoleDisplayNameInChangeRequests Value = true Click Save and then OK Notice that the updated page will show "custom.showRoleDisplayNameInChangeRequests" set with a value true. ... View more