Question
American Express
GB
Last activity: 13 Dec 2019 10:07 EST
RPA (unattended robot) and application security credentials
We are building automation scripts to be run unattended (triggered from a Pega case using the "Assign to robot queue" shape). The automation script requires application security credentials to log in to an application but we're unsure how we populate these credentials for use by an unattended robot? We've looked at the Assisted Sign-on feature but only that appears to work for RDA-type scripts where a human can enter the credentials. Any advice on how to add/store these without hardcoding the credentials in the automation script?
Accepted Solution
Pegasystems Inc.
US
You can use either the ASO Manager or the Credential Store. By default these store credentials locally on the machine using Microsoft DPAPI. ASO Manager would be the simplest to implement as there is already a ShowDialog method available. In your solution, create a small form with a button to call the ShowDialog method. The first time your solution runs on a robot you will need to enter the credentials using this option manually. This will also allow you an easy way to modify the credentials if they should change.
We also support external credential providers. There are two options currently: CyberArk and ClientCredentialProvider.
CyberArk is a commercial product that you would need to purchase, install and maintain separately.
The ClientCredentialProvider is the ability to write your own integration to provide credentials. There is a sample C# solution available in the Studio install Extras folder to give you guidance. This feature was released in Proprietary information hidden.
There will be another credential provider released in early 2020.
ANZ
IN
Hi,
There is a credential store you can lookin to. This will not completely fulfill your RPA requirement.
As this also need the credentials to be stored locally. But have a look and repost.
Accepted Solution
Pegasystems Inc.
US
You can use either the ASO Manager or the Credential Store. By default these store credentials locally on the machine using Microsoft DPAPI. ASO Manager would be the simplest to implement as there is already a ShowDialog method available. In your solution, create a small form with a button to call the ShowDialog method. The first time your solution runs on a robot you will need to enter the credentials using this option manually. This will also allow you an easy way to modify the credentials if they should change.
We also support external credential providers. There are two options currently: CyberArk and ClientCredentialProvider.
CyberArk is a commercial product that you would need to purchase, install and maintain separately.
The ClientCredentialProvider is the ability to write your own integration to provide credentials. There is a sample C# solution available in the Studio install Extras folder to give you guidance. This feature was released in Proprietary information hidden.
There will be another credential provider released in early 2020.