Skip to main content


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

Integrating credential providers in your automation

Updated on October 19, 2022

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

There are two scenarios:

  • When running an attended automation, a user is present and the user can provide the required credentials.
  • When running an unattended automation, there is no user present, and you must set up a credential provider.

Built-in credential provider

The default, built-in credential provider for attended and unattended Pega Robotic Automation sessions uses Microsoft's DPAPI (Data Protection Application Programming Interface) to store credentials locally on each computer. To learn more about DPAPI, see Configuring credentials stored using DPAPI.

External credential providers

Pega Robotic Automation also supports the following external credential providers. You can only use these providers when running unattended automation solutions:

Note: You can also set up multiple credential providers. For more information, see Setting up a custom implementation with multiple providers.

Credential providers must be supplied and managed by the client but can be interfaced directly with Pega Robotic Automation when running unattended automations. External credential providers offer the following advantages over DPAPI:

  • A single location to add and update credentials for all unattended robots
  • Secured and audited access to credentials
  • Integration with the client’s security infrastructure

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