Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Credential usage by application and type

Updated on October 19, 2022

When running unattended automations, credentials are required by the Pega RPA Service and Pega Robot Runtime. The Pega RPA Service uses the following credential types:

  • RegistrationOperator
  • WindowsUser
  • RuntimeUser

Pega Robot Runtime uses the following credential types:

  • RegistrationOperator
  • ASOManager
  • CredentialStore

Credential request life cycle

The following illustration shows how credentials are requested and how the system responds to those requests.

The credential request life cycle
An illustration that shows the life cycle of a credential request.

  • Integrating credential providers in your automation

    To enhance security, you need credentials to authenticate access with Pega Robot Manager, Windows, and applications throughout the Pega Robotic Automation process.

  • Configuring credentials stored using DPAPI

    Credentials are needed to authenticate with Pega Robot Manager, Windows, and applications throughout unattended Pega Robotic Automation sessions. The default, built-in credential provider for unattended Pega Robotic Automation sessions is Microsoft's DPAPI (Data Protection Application Programming Interface).

  • Configuring BeyondTrust Password Safe

    To keep your company and client information safe and secure, use an external credential provider, such as BeyondTrust, to authenticate with Pega Robot Manager, Windows, and other applications.

  • Configuring CyberArk

    To keep your company and client information safe and secure, use an external credential provider, such as CyberArk, to authenticate with Pega Robot Manager, Windows, and other applications.

  • Creating a client credential provider

    To keep your company and client information safe and secure, create a custom client credential provider to handle credential requests from Pega Robotic Automation and an external source.

  • Setting up a custom implementation with multiple providers

    Gather credential information from more than one provider by using the Custom provider option. For example, you can use DPAPI for RegistrationOperator and WindowsUser values while using CyberArk for AsoManager and CredentialStore values.

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us