Manage Credentials Between Applications (A2A)
The A2A (Application to Application) feature lets you manage credential requests from automated request servers. After Credential Manager provides the password, the request server submits them to access the target. Request scripts are applications that require credentials for target accounts on password management target devices. These scripts request the managed credentials by way of the A2A Client, which runs on a request server. This request server is treated like a target server but is an A2A device type.
The A2A (Application to Application) feature lets you manage credential requests from automated request servers. After Credential Manager provides the password, the request server submits them to access the target.
Request scriptsare applications that require credentials for target accounts on password management target devices. These scripts request the managed credentials by way of the A2A Client, which runs on a request server. This request server is treated like a target server but is an A2A device type.
The A2A feature uses an A2A Client that you install on a host in the customer environment. The A2A Client then has to integrate with the appliance.
This topic describes the following tasks:
The following terms are specific to A2A configurations:
Request Server:A host server where the requestor application resides and where you install the A2A Client.
A2A Client:A program that is installed on the request server. The A2A is the intermediary that communicates between the requestors and
Requestor:A program or script that requests credentials that are stored as part of an A2A target account at
PAM. To obtain credentials, the requestor communicates to the A2A Client, which then fetches the credentials from
PAMreceives the credential request, it evaluates attributes of the request server, the requesting program/script, and the user executing the requesting program. If authorized,
PAMsends the credentials to the requestor. A requester can use credentials for any task that requires credentials, such as opening connections to databases.
Target Alias:A unique name that identifies an A2A target account. An A2A target account might have multiple aliases.
Authorization Mapping:A mapping defines which requesting application or scripts can access which target accounts. Mappings implement A2A security.
To configure A2A credential management, complete the following tasks:
You do not have to complete the A2A tasks in any specific order. The only exception is for A2A deployments on an AWS AMI in an Amazon Virtual Private Cloud.
The process includes the following steps:
- Add target devices that host target accounts for use by request servers. These targets use the device type Privileged Management.
- Install the A2A Client on the remote host.
- Use the UI and integrate the A2A Client with the appliance
- Add the A2A Client as an A2A device.
- Activate this Device.
- Integrate the A2A request scripts on the A2A Client host
- Use the UI and integrate the request server with the appliance server:
- Specify the A2A request scripts
- Specify authorization mappings
Deploy an A2A Client for an AWS AMI
Follow these steps:
- Create the instance in AWS. Do not add the device before installing the A2A Client.
- Import the AWS AMI automatically into the appliance.During the import, the appliance recognizes the AWS internal IP address of the device.
- Install the A2A Client. The A2A Client registers with the appliance using the AWS internal IP address.
To process credential requests, follow these steps:
- Activate the request server (A2A Device). This step is not required when the A2A Device has already been provisioned.
- Associate the request script.
- Add the authorization mapping.
Target Identification Using Target Aliases
To manage A2A passwords, assign one or more target aliases for each target account. A target alias is a unique name that links a target server, a target application on that server, and a target account for that application. A script that is integrated with Credential Manager, uses the alias to retrieve the target account credentials from the database. The credentials enable access to the target system. With a target alias defined, target credentials are not hard-coded into scripts, allowing Credential Manager to handle password changes automatically.
The following figure shows the hierarchical structure of target accounts.
Requesting programs also identify a target account by specifying a target alias. Target aliases are global to the appliance. The aliases differ from target account names because target names can be duplicated on many hosts. An example of a duplicated name is the root account on UNIX systems.
Target aliases and groups are also used in authorization mappings.
Specifying a target alias is identical to the target alias specified by the requesting program.
If the mapping is to a target group, all accounts in the group represent the target. Grouping targets lets the requesting program/script obtain the target aliases for each target account without you configuring multiple mappings. Target groups are the most scalable way of specifying targets. However, some requesting programs might get credentials for target accounts that are not needed. To prevent this issue, configure mappings to individual aliases or set up target groups with the smallest scope possible.
See the following related content for more information: