BeyondTrust examples that include replaceable parameters
The following examples show some of the credentials that you can create using replaceable parameters.
RegistrationOperator for registration group 1:
<Credential name=”RegistrationOperator” systemName=”Registration_Group1”
runas=”APIUser” APIGROUP=”Registration” />WindowsUser using a replaceable value for the systemName attribute:
<Credential name=”WindowsUser” workgroup=”” systemName=”{MachineName}”
runas=”APIUser” APIGroup=”PegaRobot” />WindowsUser for servers with multiple Robot Runtime clients that use the accountNamePostfix attribute:
<Credential name=”WindowsUser” workgroup=”” systemName=”{MachineName}”
accountNamePostfix=”&{RobotIndex}” runas=”APIUser” APIGroup=”PegaRobot” />WindowsUser retrieving credentials using the workgroup and accountNamePostfix attributes:
<Credential name=”WindowsUser” workgroup=”{WorkGroup}” systemName=”{MachineName}”
accountNamePostfix=”&{WorkGroup}” runas=”APIUser” APIGroup=”PegaRobot” />Pooled application credentials using a hard-coded application key. (The applicationName attribute is not specified, so the Name attribute is used instead):
<Credential name=”BankerInsight” workgroup=”” systemName=”BankerInsight”
runas=”APIUser” APIGroup=”PegaRobot” />Pooled application credentials that use a replaceable parameter {AdapterFriendlyName}:
<Credential name=”Default” workgroup=”” systemName=”{AdapterFriendlyName}”
runas=”APIUser” APIGroup=”PegaRobot” />Pooled application credentials restricted to the HR work group:
<Credential name=”Default” workgroup=”HR” systemName=”{AdapterFriendlyName}”
applicationName=”{AdapterFriendlyName}” runas=”{CurrentUser}” APIGroup=”PegaRobot” />Previous topic Configure robots to work with BeyondTrust Next topic Configuring the CommonConfig.xml file for BeyondTrust