The Credentials area is a central repository for credentials in Mapp Engage.

To import or export sensitive data from an external system, use the credentials in the Credentials area. The credentials are entered in input fields in Mapp Engage. Previously, credentials were displayed as plain text. With Credentials, a Mapp Engage variable is created for user-specific data and inserted in place of the actual data. During data transmission to the external system, the variable is replaced with the actual value (for example, the password).

This variable protects the external system against unauthorized access even if an unauthorized user gains access to the Mapp Engage system. The password cannot be discovered via input fields in Mapp Engage.

In Mapp Engage, various types of user-specific sensitive data can be encrypted for a secure transfer.

  • User Name

  • User Password

  • User Account

You can also use the Credentials to configure the secure transmission of CMS messages between two connected Mapp Engage systems.

  • CMS Account

The Credentials area now also stores information for access to third-party storage systems.

  • FTP Server

  • API Endpoint

User Name​

In the Credentials area, create a record of the type ​User Name​ which encrypts only the user name. The password of the corresponding user is not affected and remains unencrypted (see ⇘ ​User Password​).

Example

A record with the type ​User Name​ is useful for applications with multiple users who have the same password for different user accounts. In this case, create one record with the type ​User Password​ and define a different record with the type ​User Name​ for all relevant users.

User Password Record

User Name Record

Sample FTP Path

Name: universalpassword

Name: user1

ftp://${encryption.user1.name}:${encryption.universalpassword.password}@Mapp.com

Name: user2

ftp://${encryption.user2.name}:${encryption.universalpassword.password}@Mapp.com

Name: user3

ftp://${encryption.user3.name}:${encryption.universalpassword.password}@Mapp.com

User Password​

In the Credentials area, create a record of the type ​User Password​, this record encrypts the user password. The user name of the user who works with this password is not affected and remains unencrypted (see ⇘ ​User Name​).

Example

A record with the type ​User Password​ is useful when different applications require the same user name but have different passwords. This discrepancy can result from, for example, different requirements for passwords. In this case, create one record with the type ​User Name​ and define a different record with the type ​User Password​ for all relevant users.

User Name Record

User Password Record

Sample FTP Path

Name: universaluser

Name: passwordx

ftp://${encryption.universaluser.name}:${encryption.passwordx.password}@Mapp.com

Name: passwordy

ftp://${encryption.universaluser.name}:${encryption.passwordy.password}@Mapp.com

Name: passwordz

ftp://${encryption.universaluser.name}:${encryption.passwordz.password}@Mapp.com

User Account​

In the Credentials area, create a record of the type ​User Account​. This record type encrypts both the user name and user password in a single record. It is also easier to insert the placeholder because the placeholder for the user name and password is generated with the name from a single record.

Example

A record with the type ​User Account​ is useful when an application requires that the user name and password are used together. To ensure that these passwords are not created separately with different names with the ​User Name​ and ​User Password​ types, use the type ​User Account​.

User Account Record

Sample FTP Path

Name: user1

ftp://${encryption.user1.name}:${encryption.user1.password}@Mapp.com

CMS Account​

For customers with multiple Mapp Engage systems, a CMS Account record can be used to interface with an external system to import CMS messages. With the help of the ​CMS Account​ type, the URL of the external system and the user data of an API user are encrypted.

The record with the ​CMS Account​ type is accessed with an API during the message creation process.

Hint:

Records with the type CMS Account cannot be reused within Mapp Engage. They are only required to interface with the external system

Example

A CMS Account record is useful when there are CMS messages in an external system that are to be imported for sendout to groups stored in a separate system.

CMS Account Record

Placeholder

Name: cmsaccount

URL: ${encryption.cmsaccount.cmsAccountURL}

User Name: ${encryption.cmsaccount.cmsAccountUser}

Password: ${encryption.cmsaccount.cmsAccountPassword}

FTP Server​

​Credentials​ allows customers to store credentials to third-party FTP servers securely. The credentials are encrypted and stored securely as reusable credential records.

In ​Credentials​, you specify access to the third-party infrastructure for reuse.

Save your user name and password for a third-party FTP server in the Credentials area. If you must change your password for the FTP server, you only change the information in the Credentials once. Mapp Engage automatically retrieves the new password whenever the password is needed.

Example

Previously, the file location and password were stored separately. Save your user name and password for a third-party FTP server in the Credentials. If you must change your password for the FTP server, you only change the information in the Credentials once. Mapp Engage automatically retrieves the new password whenever the password is needed.

API Endpoint​

Each API access method has an endpoint. This endpoint is defined with the account name and password.

This API endpoint is used in Automations and Whiteboard to send an http request.

In the content store, you specify access to the third-party infrastructure for reuse.

Save your user name and password for API access in the Credentials area. If you must change your API credentials, you only change the information in the Credentials once. Mapp Engage automatically retrieves the new information whenever this information is needed.

The name of the record can be the API endpoint in the format servernam/folder/folder. Be pragmatic and use descriptive names or descriptive server paths when the path is the name of the record

Example

API Endpoint

Path

Group and clone

URL: mysystem.com/API/group_and_clone.