Table of Contents

CyberArk support in Pega Robotic Automation

Build automations that work seamlessly in a secure environment by combining Pega Robotic Automation 19.1 with CyberArk Application Access Manager (AAM) 9.1 and later.

CyberArk Application Access Manager (AAM) was previously known as Application Access Manager (AIM).

AIM is integrated with the Pega RPA Service and Pega Robot Runtime. The integration is an End Point integration with no Middle Tier or Central Server. Credential retrieval is triggered by the Pega RPA Service and Pega Robot Runtime:

  1. When the service starts, the Pega RPA Service retrieves RegistrationOperator credentials. These credentials are used to log in to the Pega Robot Manager.
  2. When the Pega Robot Manager tells the Pega RPA Service to start the robot, the Pega RPA Service retrieves the WindowsUser credentials and performs a Windows log in.
  3. After the robot is logged in, the Pega RPA Service looks for the RuntimeUser credentials.
    • If there are RuntimeUser credentials, Pega Robot Runtime is started by using these credentials.
    • If there are no RuntimeUser credentials, Pega Robot Runtime is started by using the logged in user’s credentials.
  4. When Pega Robot Runtime starts, the RegistrationOperator credentials are retrieved and Pega Robot Runtime logs in to the Pega Robot Manager.
For Robotic Processing Automations, the Registration Operator and WindowsUser credentials are required, and the RuntimeUser credentials are optional.

A Robotic Automation solution can use the ASO Manager component or the Credential Store component to retrieve applications credentials. You can configure the ASO Manager and Credential Store to retrieve these credentials from CyberArk.

For more information, see Integrating CyberArk and Pega Robotic Automation. See also the following links:

 

Suggest Edit

100% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.