Using Pega Access to control integration behavior
Use Pega Access to limit the amount of information that you store locally.
CredMgrUI.exe
utility to store the required
BeyondTrust API groups and BeyondTrust Runas users locally.
Enable the UseCurrentUserForASO and UseCurrentUserForCredStore attributes to control the Runas user that requests application credentials from the ASO Manager or the Credential Store, respectively.
- Open BeyondTrust Password Safe.
- Enable the appropriate options for your security needs:
- If you enable the UseCurrentUserForASO option,
requests for credentials that are made to the ASO Manager use the current
logged-in user instead of the Runas user who is specified in the
CredentialManagerConfig.xml
file. - If you enable the UserCurrentUserForCredStore
option, requests for credentials made to the Credential Store are made with
the current logged-in user instead of the Runas user who is specified in the
CredentialManagerConfig.xml
file.
Note: If the current user is a domain user, add the user to the user group in BeyondTrust as an Active Directory user.
If the current user is logged into the computer locally, add the user to the user group in BeyondTrust as a BeyondTrust user and format the name as
username/machinename
. - If you enable the UseCurrentUserForASO option,
requests for credentials that are made to the ASO Manager use the current
logged-in user instead of the Runas user who is specified in the
- Save your selections and exit BeyondTrust Password Safe.
Previous topic Using the Credential Manager utility to store API keys Next topic Configuring CyberArk