Before beginning the procedures below, make sure you have configured your CyberArk® integration.
You must add the login credentials under which your Robot runs. If you have multiple Robots, perform this procedure for all of them. This procedure applies to both local and domain users. From the CyberArk® PVWA interface, follow these steps:
- On the Accounts tab, click Add Account. The Add Account page is displayed.
- Select Windows in the System Type list.
- On the Assign to Platform tab:
a. select Windows Desktop Local Accounts if the Robot user is local.
b. select Windows Domain Account if the Robot user is part of an Active Directory.
- On the Store in Safe tab, select the safe you previously created.
- On the Define Properties tab, populate the following fields:
The name of the user under which the Robot runs.
Password and Confirm Password
Type the password that belongs to the user under which the Robot runs.
Customize Account Name Toggle
Enabled. Type the machine or domain name, and the Robot username. The same name needs to be used in Orchestrator when defining the credential for the robot.
- Click Save. The account is saved. Orchestrator uses this to retrieve the Robot credentials when it needs to, if you have the Robot provisioned in Orchestrator.
After performing the steps above, you have to provision the Robot in Orchestrator. As you are now using CyberArk® to store your passwords, please note that in the Provision Robot window, you no longer have to add the password. However, the user is still mandatory.
When provisioning the Robot in Orchestrator, add the username as you normally would:
- for local users - the actual username, such as
- for domain users - the username and domain it runs under, in the
DOMAIN\usernameformat, such as
Based on the user provided for the Robot, Orchestrator searches for a match in CyberArk®. When a match is found, the corresponding password is retrieved.
When making changes to the password in Cyberark Application Password Provider, please keep in mind that it might take a few minutes for it to be propagated in Orchestrator due to AIM's cache system.
Updated about a month ago