Provisioning Command node does not save attribute values correctly in RSA Identity Governance & Lifecycle
Originally Published: 2018-09-05
Article Number
Applies To
RSA Version/Condition: 7.0.1, 7.0.2, 7.1.0
Issue
When adding a Provisioning Command node in a Fulfillment Workflow, type some static value with one or more commas in the command's fields and then save the workflow. The application actually splits these values by commas and places each split value in each of the command's fields/attributes.
- Configure Fulfillment Workflow with Provisioning Command node
- Type some static value with a comma in the command's fields:
- Save the workflow and check the values again; you will notice that the value with comma was split and placed into each parameters. This doesn't produce any error in the logs while saving the workflow.
Cause
Resolution
- RSA Identity Governance & Lifecycle 7.0.2 P08
- RSA Identity Governance & Lifecycle 7.1.0 P02
Workaround
- Add the variable using the +)sign under the Variables section.
- Once the variable is added, right click on the value field for the desired name parameter and select the variable to add to the value field.
Make sure to select Business Source and Command field before setting the values.
Related Articles
No email in certificate mail attribute which KCA needs for renewal notices 2Number of Views Unable to Authenticate to vCenter – "Signature Certificate Verification Failed: Signature Does Not Match" 22Number of Views User Event Monitor Messages for Cloud Access Service (20601 - 38000) 329Number of Views User Event Monitor Messages for Cloud Access Service (1501 - 20406) 367Number of Views System Event Monitor Messages for Cloud Access Service 171Number of Views
Trending Articles
RSA Authentication Manager 8.9 Release Notes (January 2026) RSA announces the availability of the RSA SecurID Hardware Appliance 230 based on the Dell PowerEdge R240 Server How to troubleshoot Oracle database ORA-04030 errors in RSA Identity Governance & Lifecycle RSA Authentication Manager Upgrade Process Microsoft SQL Server Collectors can no longer connect to the SQL Server database after upgrade to Microsoft SQL Server 201…
Don't see what you're looking for?