1. Mirth Connect
2. Home
3. Configuration (Official)

Created by Gerald Bortis, last modified by Jacob Brauer on Oct 08, 2013

Icon

These properties have been added as of Mirth Connect 2.2.

There are several "hidden" properties that you can set to configure extra encryption features in Mirth Connect.

To configure the general encryption settings that will be used for things like message and password encryption, set the following properties in $MIRTH/conf/mirth.properties

# The algorithm to use for encryption (DES, AES, etc.)
encryption.algorithm = AES

# The key length
encryption.keylength = 128

# The algorithm to use for one-way hashing (MD5, SHA, etc.)
digest.algorithm = SHA256

# The security provider to use for all encryption and hashing.
security.provider = org.bouncycastle.jce.provider.BouncyCastleProvider

You can also enable encryption for exports. This means that anything that you export through the Administrator (channels, messages, etc.) will be first encrypted using the settings specified. Note that this also means that if you want to import these files you will need to share the encryption key and use the same settings.

# Enables encryption/decryption of export/import through the Administrator.

encryption.export = 1

You can also choose to enable properties in the mirth.properties file that contain password.

# Enabled encryption of properties with passwords.

encryption.properties = 1

To encrypt your plain text password:

1. Stop the Mirth Connect server/service
2. Add/set the value of encryption.properties to 1
3. Set the database.password property to your password
4. Restart the server/service

You will notice that the database.password property is now encrypted. Do not modify the property.

Document generated by Confluence on Nov 11, 2019 08:40

Atlassian