In general, the principle of least privilege should be followed, and only Administrators should have access to the installation directory that Mirth® Connect is installed into. If installed on a dedicated machine, that machine should only be accessible to said administrators. If installed on a shared machine, it should be done in such a way that the Connect installation directory is only accessible by administrators.
Notes on specific folders inside the installation directory:
- appdata: The Application Data Directory stores configuration and temporary files used by Mirth® Connect during runtime. Take note of:
- configuration.properties: By default this file is used to store the current state of the Configuration Map. However in mirth properties you can choose to store the configuration map in the database, or you can select a different file location. For example if you have a separate network storage location specifically for secure files, you could choose to store the configuration map file there instead.
- keystore.jks: This is a critical file that stores your server's local certificate keypair (for the web server and API), and also the secret key used for encrypting message data, exports, and anything else. Any messages/channels/etc that are encrypted by Mirth® Connect use the encryption key stored in this file, so if this file is lost, those encrypted messages will be irrecoverable. The location of this file can be configured in the mirth.properties File. This file is encrypted, and the store-password / key-password are set in as well.
- conf: The Configuration Directory contains the main configuration files Mirth® Connect needs to start up correctly. Take note of:
- mirth.properties: This is the main configuration file for Mirth Connect. It contains sensitive information such as your database username/password and the storepass/keypass for the keystore. You can change the location of various files and folders, such as the appdata folder or the keystore.jks file
