Web Services Change Requests do not display usernames of duplicate accounts in RSA Identity Governance & Lifecycle
2 years ago
Originally Published: 2019-08-09
Article Number
000041215
Applies To
RSA Product Set: Identity Governance & Lifecycle
RSA Version/Condition: 7.0.2, 7.1.0, 7.1.1

 
Issue
When creating change requests via Web Services in RSA Identity Governance & Lifecycle, sometimes there is no username associated with an account.
 
User-added image


The following error in the aveksaServer.log shows there is a duplicate account:
 
06/04/2019 05:50:54.037 INFO (Worker_actionq#Script Queue - Normal#WPDS_3078) [com.aveksa.server.workflow.scripts.nodes.RESTWebServiceNode] Starting of REST Web Service Request. 06/04/2019 05:51:05.986 INFO (Worker_actionq#Script Queue - Normal#WPDS_3078) [com.aveksa.server.workflow.webservices.rest.client.RestClient] REST Request Completed with status code: 200 and Message: OK 06/04/2019 05:51:05.987 INFO (Worker_actionq#Script Queue - Normal#WPDS_3078) [com.aveksa.server.workflow.scripts.nodes.RESTWebServiceNode] Invocation of external Webservice using REST request (POST) is completed 06/04/2019 05:51:05.988 INFO (Worker_actionq#Script Queue - Normal#WPDS_3078) [com.aveksa.server.workflow.scripts.nodes.RESTWebServiceNode] End of REST Request Invocation 06/04/2019 05:51:09.656 INFO (default task-62) [com.aveksa.server.command.CreateChangeRequestCommand] Found more than one account named grc1 for business source 82
 
Please refer to RSA Knowledge Base Article  000030327 -- Artifacts to gather in RSA Identity Governance & Lifecycle to find the location of the log files for your specific deployment.
Cause
This is a known defect reported in engineering ticket ACM-98806 and occurs when an application or directory has a duplicate account (one deleted and one active.)
 
Resolution
This issue is resolved in the following RSA Identity Governance & Lifecycle patches:
  • RSA Identity Governance & Lifecycle 7.0.2 P13
  • RSA Identity Governance & Lifecycle 7.1.0 P07
  • RSA Identity Governance & Lifecycle 7.1.1 P01
Workaround
9 August 2019 -- Apeksha Shetty
Article creation

16 August 2019 -- Apeksha Shetty
Since 7.0.2 is going EOL Aug 2019 thought not to include it in the KB version changes. Anyways have added this version and also the other jira number.

Diane McCoy -- August 22, 2019 
Reviewed article. Modified title, grammar, removed code from code block since was too long. Made sure only the error was red and not all the informational messages, etc.