Enterprise 11: Use Credential Vault to store user IDs, passwords, and other sensitive data
- Última atualização2022/08/10
Enterprise 11: Use Credential Vault to store user IDs, passwords, and other sensitive data
Store all user IDs and passwords in the Credential Vault in the Control Room, which is then referenced in the bot code.
Prerequisites
Important: Never hardwire user IDs and passwords ed as variables in
tasks because this introduces a security risk.
Procedure
Next steps
Now the Credential is available to use as an input for values in Task Bots and MetaBots.
Following are some important facts about using variables:
- Developer-created variables can be used with most Automation Anywhere commands.
- All command fields with the light bulb icon support variables.
- Press the F2 function key to list all user and system variables that are available for a selection.
- When a Task Bot runs, Automation Anywhere replaces the variable name with the actual value of the variable.
Important: Credential
variables are not visible until a Control Room user with
Locker Admin privileges enables the setting in the Control Room. When the setting is enabled, credential
variables are available for passing as parameters from one Task Bot/MetaBot Logic to another Task Bot/MetaBot Logic. Read Passing parameters from and to MetaBot Logic for details.
For more information on how to use the Credential Vault, see Credentials- Overview and Credential variables.
Note: If a Task Bot or MetaBot is run directly
from the Control Room, the credentials used from the Credential Vault might need to be manually reassigned. For
example, if a MetaBot is run from the Control Room, open the MetaBot and reassign any input parameters that are
stored in the Credential Vault.