Goal
To create a credential record that securely stores and reuses access data for an external system — for example a transfer (FTP) server, Amazon S3, Google Cloud Storage, or CMS access to a connected Mapp Engage system. Instead of showing login data in plain text, Mapp Engage stores it as an encrypted credential and generates placeholders that you use in its place.
Prerequisites
You have permission 160 (System Administration: Create and Edit Credentials Records).
Depending on the credential type, you also need the provider-specific access data listed under Credential Types and Parameters.
Background Information
The Credentials function (Transfer Security) manages sensitive data used to connect to external systems. You can encrypt the user name, the password, or the entire user account. During data transfer, Mapp Engage replaces the placeholder with the actual value, so the login data is never exposed in the interface. For the available credential types and how they are used, see Credential Types in Mapp Engage.
Procedure
In the main navigation, click User Management > Permissions > Credentials.
Click Create.
In the Name field, enter a unique name (up to 50 alphanumeric characters, lowercase only). Optionally, add a Description.
From the Type drop-down list, select the credential type. The available fields adjust to the selected type.
Enter the required parameters for the selected type (see Credential Types and Parameters).
Click Save. Where available, use Test Connection to verify the connection. Mapp Engage generates the placeholders for the credential; for a transfer server, use these placeholders to construct the FTP path.
Credential Types and Parameters
Credential Type | Required parameters | Notes |
|---|---|---|
Transfer Security (server / FTP) | The user name, password, or full user account that you want to encrypt. | Mapp Engage generates placeholders that you insert into the FTP path instead of the plain login data. |
Amazon S3 Account | User Key, Secret Key, Region Name, Bucket Name. | Only one credential record can be created per S3 bucket. |
Google Storage Account | JSON credentials file (upload), Google Project ID, Storage Bucket Name. | Requires a Google Cloud Storage service account (not a user account) with full permissions for the bucket. Only JSON files are accepted. Only one credential record per bucket. |
CMS Account | URL of the providing Mapp Engage system, plus the username and password of an account on that system. | That account needs permissions 103 (System Administration: Use API 2.0) and 223 (CMS: View all CMS Messages). After saving, open the Select CMS Message window to verify that access is set up. |
Delete a Credential
A credential must be archived before it can be deleted.
In the main navigation, click User Management > Permissions > Credentials.
Select the record and click Archive.
Filter the Credentials Overview by the status Archived.
Select the archived record and click Delete.