Skip to main content

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

Configuring the CredentialManagerConfig.xml file for BeyondTrust

Updated on October 19, 2022

Prepare a robot for integration with BeyondTrust and to store shared secrets by editing the CredentialManagerConfig.xml file.

To configure a robot to integrate with BeyondTrust, perform the following steps:
  1. Open the CredentialManagerConfig.xml file in a text editor.
  2. In the CredentialManagerConfig.xml file, add a Provider element and specify the baseUrl of your BeyondTrust server. The following is an example:
    <Provider name=”BeyondTrust” baseURL=”https://<server-redacted>/BeyondTrust/api/public/v3” >
  3. Add Credential elements to map to the required credentials. In the name element, enter the credential name, and then define the element by specifying the following attributes:
    1. For the RegistrationOperator attribute, enter a reserved name that is used by the RPA Service and Robot Runtime. Only one element is required. The workgroup attribute is ignored.
    2. For the WindowsUser attribute, enter a reserved name that is used by the RPA Service. At least one credential is required.
    3. For the RuntimeUser attribute, enter a reserved name that is used by the RPA Service.
    4. For the Application keys/names attribute, enter a name that matches the application keys that are specified in the ASO Manager or the Credential Store.
    5. For the Default attribute, if there is no direct application key match for the ASO Manager or the Credential Store, the system tries to match a credential named "Default." When matching "Default," the system first tries to match the workgroup attribute. If there is no match, the system tries to match an entry that has no work group. If there still is no match, the request fails. The system does not search for the “Default” element when it processes a request for the RegistrationOperator, WindowsUser, or RuntimeUser attributes.
  4. For the workgroup element, specify the Robot Manager work group that the robot is assigned to. If the credential name is found but it does not have a matching work group, the request matches an element that has a blank work group.
    Unattended RPA allows for a unique domain and Runas user name/password for each work group that the robot can work in. Use this setting to specify different credentials for each work group.
  5. If you are setting up robots to be used with the Server Bot Framework, use the Robot Index field to indicate which robots these credentials are for. For more information, see Server Bot Framework.
  6. When you are finished, click Add.
  • Previous topic Configuring the CommonConfig.xml file for BeyondTrust
  • Next topic Using the Credential Manager utility to store API keys

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