Skip to content

4.4.0 Upgrade Guide

Jump to bottom
nrupley edited this page Jul 10, 2023 · 6 revisions

Administrator Launcher 1.4.0 Released

We've released a new version of the Mirth Connect Administrator Launcher that now comes bundled with Java (OpenJDK) 17 rather than Oracle Java 8. There are also new AArch64 releases for ARM compatibility on Mac M1 machines.

If you are launching the Administrator GUI for older versions of Mirth Connect that don't support Java 17 or OpenJDK, then you may need to download Oracle JRE 8 and set it as your "Custom" Java Home in the launcher settings for that server.

Default Digest Algorithm Changed

We've changed the default digest/hash algorithm from SHA256 to PBKDF2WithHmacSHA256. In addition, the default iteration count was changed from 1000 to 600000. Support for Argon2 was also added. This was done to conform with modern password security recommendations.

If you had already explicitly set digest.algorithm, then no changes are made, Mirth Connect will still use the digest algorithm that you have set.

If you had not already explicitly set digest.algorithm, then the new default algorithm will be used going forward. New "fallback" properties will be set to the old defaults, so old digest values can still be verified. When a user updates their password, the digest value will be updated to use the new algorithm at that time.

Updating the Digest Algorithm

In order to make sure you can still login with your existing credentials (which used the old digest settings), you will want to make sure to set the "fallback" digest settings in mirth.properties. For example:

  • digest.fallback.algorithm = SHA256
  • digest.fallback.saltsizeinbytes = 8
  • digest.fallback.iterations = 1000
  • digest.fallback.usepbe = 0
  • digest.fallback.keysizeinbits = 256

Then, update the digest.* settings to the new algorithm/etc you want to use.

After restarting Mirth Connect, it will use the new digest settings for all new digest values. It will also use the "fallback" settings to verify old digest values.

To use the new digest value for your stored password hash in the database, update your user password in the Administrator.

Clone this wiki locally