fusionauth-issues
fusionauth-issues copied to clipboard
Installation on postgres fails when MD5 function disabled
Installation on postgres fails when MD5 function disabled
Description
New deployments of the latest FusionAuth (1.53.2) are failing on Azure Database for PostgreSQL Flexible Server version 15.8 with the error below.
Note that Azure does not allow specifying minor versions of Postgres, and auto-upgrades all PostgreSQL Flexible Servers to the latest minor release, potentially breaking existing installations.
fusionauth-86b55b4f87-d9xgs fusionauth -- Initialize migrations so they don't run on new installs │
│ fusionauth-86b55b4f87-d9xgs fusionauth INSERT INTO migrations (name, run_instant) │
│ fusionauth-86b55b4f87-d9xgs fusionauth VALUES ('io.fusionauth.api.migration.guice.Migration_1_8_0', 0), │
│ fusionauth-86b55b4f87-d9xgs fusionauth ('io.fusionauth.api.migration.guice.Migration_1_9_2', 0), │
│ fusionauth-86b55b4f87-d9xgs fusionauth ('io.fusionauth.api.migration.guice.Migration_1_10_0', 0), │
│ fusionauth-86b55b4f87-d9xgs fusionauth ('io.fusionauth.api.migration.guice.Migration_1_13_0', 0), │
│ fusionauth-86b55b4f87-d9xgs fusionauth ('io.fusionauth.api.migration.guice.Migration_1_15_3', 0), │
│ fusionauth-86b55b4f87-d9xgs fusionauth ('io.fusionauth.api.migration.guice.Migration_1_30_0', 0), │
│ fusionauth-86b55b4f87-d9xgs fusionauth ('io.fusionauth.api.migration.guice.Migration_1_42_0', 0); │
│ fusionauth-86b55b4f87-d9xgs fusionauth . Cause: org.postgresql.util.PSQLException: ERROR: could not compute MD5 hash: disabled for FIPS │
│ fusionauth-86b55b4f87-d9xgs fusionauth 2024-09-27 08:35:30.978 PM INFO com.inversoft.maintenance.db.JDBCMaintenanceModeDatabaseService - [6ZLRZw] Attempting to unl │
│ fusionauth-86b55b4f87-d9xgs fusionauth 2024-09-27 08:35:30.979 PM INFO com.inversoft.maintenance.db.JDBCMaintenanceModeDatabaseService - [6ZLRZw] Unlock completed │
Calling the postgres md5 function produces the same error:
SELECT MD5('PostgreSQL MD5');
ERROR: could not compute MD5 hash: disabled for FIPS
This error appears to be caused by Microsoft disabling MD5 support in Azure Postgres 15.8.
Note that MS re-enabled the MD5 function per this comment, but it is unclear how long it will be enabled.
Searched briefly and didn't find any long term plans to remove the md5 function from postgresql, but it still might be nice to move towards FIPS compliance.
Community guidelines
All issues filed in this repository must abide by the FusionAuth community guidelines.