Vault key configuration
Use the Vault key configuration to supply a vault key that provides
access to an IBM® App Connect Enterprise vault that stores credentials to connect to
secured resources.
Vault key configuration works
with the Vault configuration. Use both of these configurations if your IBM App Connect Enterprise
Toolkit integration is configured to connect to secured
resources.
The Vault and Vault key configurations were deprecated in IBM App Connect Operator 12.11.0. Instead, use the Vault archive
and Vault archive key configurations to provide encrypted credentials that are
exported from an integration server vault or external directory vault in IBM App Connect Enterprise. You can create Vault archive and
Vault archive key configurations for integration runtimes at version 13.0.3.0-r1 or
later.
Summary of key details
- File name or type
- String value
- Does the file contain secrets?
- Yes
- Location of imported or extracted data
- Not applicable (the value is passed to the integration runtime when it starts)
- Maximum number of vault key configurations allowed per integration runtime
- One
The Vault key value
The Vault Key configuration requires a string value that the deployed
integration uses to access the credentials in the vault. The vault key must be at least 8 characters
in length. You can specify only one vault key per integration runtime. When the runtime starts, it
reads the value of the vault key in the configuration.
The vault key must match the value that you provided when the vault was created. This vault key is also used when you use the App Connect Enterprise Console to run the mqsivault command or mqsicredentials command. For more information, see Configuring encrypted security credentials and Connecting client applications in the App Connect Enterprise documentation.
Vault key
configuration on the Configurations tab of the Manage
page and enter the string value of the vault key into the text editor. For more information, see
Providing credentials and secrets in configurations.