Element

Description

Providers

Contains a list of available credential providers. Choose from the following credentials providers:

• DPAPI

• CyberArk

• Custom

Providers/Provider name=”DPAPI”

This credential provider has no additional parameters.

Providers/Provider name=”CyberArk”

This credential provider includes the following parameters:

• applicationID – Enter the CyberArk ApplicationID that is used to retrieve the credentials. CyberArk ApplicationIDs can be secured using the IP address, OS User name, application path, application hash, and other means. The ApplicationID should be provided by a CyberArk administrator.

• adminOperator – Enter a value that can be used as a replaceable value for individual credentials.

Credentials

Lists the individual credentials for CyberArk. When mapping individual credentials, use the following dynamic values, which are determined at runtime:

• {AdminOperator}

• {RobotName}

• {AdapterFriendlyName}

Using a strategy that stores credentials in CyberArk using values that are unique but may be constructed using these dynamic values can reduce the need for individual customization for each robot.

For each credential, include the following information:

• safe

• folder

• objectName

Credentials should be mapped to CyberArk based on these attributes for each credential provided by a CyberArk administrator.

Credentials/Credential name=”RegistrationOperator”

This credential retrieves the Registration Operator. This name is a reserved name in the system. Include the following information:

• safe

• folder

• objectName

Credentials/Credential name=”WindowsUser”

This credential retrieves the Windows user. This name is a reserved name in the system. Include the following information:

• safe

• folder

• objectName

Credentials/Credential name=”RuntimeUser”

This credential retrieves the Runtime user. This name is a reserved name in the system. Include the following information:

• safe

• folder

• objectName

Credentials/Credential name=”{ASOManagerKey}”

This credential retrieves a value that is defined in the ASO Manager. This name is defined in an adapter credentials property configuration screen. Include the following information:

• safe

• folder

• objectName

Credentials/Credential name=”{CredentialStoreKey}”

This credential retrieves a value that is defined in the Credential Store. The solution developer defines this name and it must include the following information:

• safe

• folder

• objectName

Credentials/Credential name=”Default”

This credential retrieves a value when a request does not match another credential. You can use a credential naming strategy to reduce the need to individually specify credentials. Include the following information:

• safe

• folder

• objectName

The following is an example of how you could use this credential type:

<Credential name="Default" safe="{RobotName}" folder="root" objectName="{AdapterFriendlyName}-{RobotName}" />

With these settings, each robot would have its own safe and each application credential would have an objectName with the Adapter Friendly Name and the Robot Name separated by a dash. Using this pattern, you can store many credentials in a safe that is only accessible by this robot and you do not need to list these individually.

Credentials/Credential name=”Custom”

This credential contains a list of CustomProviders that define which provider is responsible for providing each of the credential types. Custom providers are evaluated in the order that you list them, with first provider winning all ties.

Enter at least two CustomProviders, one for DPAPI and one for CyberArk.  Specify each of the values and mark them True or False.

CustomProvider name=”CyberArk”

Use this custom provider to define the attributes for CyberArk. Set each attribute to True or False. If you enter True, then CyberArk provides this credential type. This custom provider has the following attributes:

• registrationOperator

• windowsUser

• runtimeUser

• asoManager

• credentialStore

CustomProvider name=”DPAPI”

 Use this custom provider to define the attributes for DPAPI. Set each attribute to True or False. If you enter True, then DPAPI provides this credential type.This custom provider has the following attributes:

• registrationOperator

• windowsUser

• runtimeUser

• asoManager

• credentialStore