Skip to main content

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

Integration with Pega Access (Optional)

Updated on October 19, 2022

To maintain only one API key on the robot, and still have access to an unlimited number of API keys that are retrieved from BeyondTrust when needed, you can set up Pega Access.

Pega Access is a single API key that is stored on the Robot Runtime computer, and provides access to configuration information that is read from BeyondTrust on startup. Each of these additional keys can be individually secured. Using this feature reduces the need for maintenance on individual robots.

Integration with Pega Access
Optionally integrating Robot Runtime with Pega Access.

Pega Access offers several advantages:

  • You can set up each computer a minimal set of shared secrets, with the API keys that are not stored locally being retrieved from BeyondTrust on demand.
  • Each API key has authentication rules that control who can use the key to retrieve credentials. Using more API keys allows more granular control of access to credentials.
  • You can change API key values (except for the Pega Access API key) in BeyondTrust without the need to update individual computers.

To implement Pega Access, you create a special asset, a managed account, a user group, and a user with reserved names. When present, the integration uses Pega Access if an API key is not found locally.

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us