Configuring an IBM App Connect Enterprise vault

Before you can store encrypted credentials for an integration node or integration server, you must configure an IBM App Connect Enterprise vault. You can configure a vault by using commands, the IBM App Connect Enterprise Toolkit, or the administration REST API, and you can view credentials in the vault by using the Toolkit or the web user interface. Credentials can be stored in an integration server vault, an integration node vault, or an external directory vault.

Integration server vault

An integration server vault is an App Connect Enterprise vault that is configured to be used by a specific integration server, and is located in the integration server's work directory.

Integration node vault

An integration node vault can be used by the integration node, the integration node-wide HTTP listener, and any integration servers that are managed by the integration node. Credentials that are stored in an integration node vault can be accessed by all the integration servers that are managed by the integration node, which means that credentials to be stored in one place and shared by all the integration servers that are managed by the integration node. You can also configure an integration node to use an external directory vault. Credentials that are stored in the external directory vault are available for use by the integration node, the integration node-wide HTTP listener, and any integration servers that are managed by the integration node.

External directory vault

An external directory vault is an App Connect Enterprise vault that can be shared by any number of integration nodes and servers. You choose the location in the file system in which to create the vault, and then configure each integration node or server to use it by specifying its unique location.

The following videos demonstrate how to use the vaults that are available in IBM App Connect Enterprise:

• Credential Management in the Toolkit.
• An example of managing credentials using the Toolkit.
• Using dynamic HTTP credentials to access a secured back-end service.
• Introducing the external directory vault.
• Using the external directory vault while developing flows in the Toolkit.