Password Type field does not move with Process when using the Export / Import actions in Process Automation
Article ID: 110243
Updated On:
Products
CA Process Automation Base
Issue/Introduction
When importing processes from one Orchestrator to another, "Password" field types are not being imported and the process is failing.
Why does this happen and can we prevent this?
Environment
Release: ITPASA99000-4.3-Process Automation-Add On License for-CA Server Automation
Component:
Component:
Resolution
This is by design to protect those passwords.
A password field can be modified and reset from a "Password" type field to a "String" type field which will expose the password.
Due to this potential security issue "Password" type fields are not moved from one Orchestrator to another with the export / import actions.
Please consider using a named global datasets to store connection details such as username and password and you call that from your processes to retrieve the password at runtime.
That way when you export your process and import into a new environment as long as the named dataset is in the same location with the same name, the imported process it will pick up the new environments values and use the new environments details.
A password field can be modified and reset from a "Password" type field to a "String" type field which will expose the password.
Due to this potential security issue "Password" type fields are not moved from one Orchestrator to another with the export / import actions.
Please consider using a named global datasets to store connection details such as username and password and you call that from your processes to retrieve the password at runtime.
That way when you export your process and import into a new environment as long as the named dataset is in the same location with the same name, the imported process it will pick up the new environments values and use the new environments details.
Feedback
Yes
No
Powered by
