Integration with Pega Access (Optional)
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.
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.
- Configuring Pega Access
Reduce the need for maintenance on individual robots by configuring Pega Access.
Previous topic Integration with Password Safe Next topic Configuring Pega Access