For the purpose of this guide, a Simple vault type is used in our examples to securely store
database information. The Simple vault type makes use of the secrets.txt file. The
Simple vault type is not recommended for use in production environments.
The Simple Key Vault requires a text file, which contents will be encrypted, and is primarily used to store the credentials of database users. The file is only used if the vault type is set to Simple, which will be configured on the next page.
The Key Vault file can, among other things, store the encrypted username, password, and URL for databases in
the AMT environment. On startup, the values in this file are encrypted, at which point these values should no longer be
manually modified. The file is analyzed for an (invisible) null character followed by a binary marker:
at the end of the file to verify that it is
encrypted.
In the instructions below, keys and values are added to the Key Vault file. Should the file be manually updated after encryption, then please use the original unencrypted Key Vault sample file (called secrets.txt). The block below serves as a suggestion for names to use as keys for the Username, Password, and URL.
systemDatabaseUser:=<Username>
systemDatabasePassword:=<Password>
systemDatabaseURL:=<URL>
applicationDatabaseUser:=<Username>
applicationDatabasePassword:=<Password>
applicationDatabaseURL:=<URL>jdbc:postgresql://<Server>:<Port>/<Database> for PostgreSQL databases.
The keys that are defined above are used to configure the database on the next page.
| Extra information |
|---|
| See the File: Key Vault page for more information. |
- id: config1. Multiple configurations can be added and used simultaneously.