Boomi to Postgres connection error

Question

Hello,

I am trying to create a connection from Boomi to Postgres DB on Azure. My Postgres instance is a managed DB instance and I have the Boomi IP whitelisted via Networking settings. The user ID and Password works fine when I try from my local laptop but when I try from Boomi, I get below error:

Browse operation failed; Caused by: Unable to connect to database; Caused by: Unable to open database connection. FATAL: no pg_hba.conf entry for host "xx.xx.xx.xx", user "DB_User", database "Test_DB", no encryption; Caused by: FATAL: no pg_hba.conf entry for host "xx.xx.xx.xx", user "DB_User", database "Test_DB", no encryption

What am I missing with the configuration here? I am using JDBC driver for connecting to Postgres. I did restart the Postgres instance after updating the firewall rules but I still get the same error.

Answer 1

Hi @Balvinder Sabherwal

Based on the information shared so far, the issue does not appear to be related to database credentials. Rather, it points towards how the connection request is being initiated from the Boomi runtime environment.  

Could you please verify the following:

Ensure that the source IP address shown in the error message is whitelisted in the Azure Database for PostgreSQL firewall rules.

Confirm that SSL is enabled and being enforced on the client connection.

Verify that the JDBC driver version being used by Boomi supports SSL connections to Azure Database for PostgreSQL.

Review the Boomi connector configuration to ensure the SSL parameters are being passed correctly during connection establishment.

Answer 2

The important part of the error is “no encryption.” The request is reaching PostgreSQL, but the server sees a non-TLS connection. Because you already added sslmode=require, the most likely issue is that Boomi is not passing that property to the PostgreSQL JDBC driver actually used by the Atom/Molecule.

Check these items in order:

1. Use the full URL format: jdbc:postgresql://<server>.postgres.database.azure.com:5432/Test_DB?sslmode=require. If the URL already has parameters, add it with &sslmode=require. If Boomi exposes separate driver properties, also set sslmode=require there.
2. Confirm the connection uses a current PostgreSQL JDBC driver rather than a generic or older driver, and restart the Boomi runtime after replacing the driver.
3. Compare the IP shown in the PostgreSQL error with the Azure firewall rule. Boomi Atom Cloud or a Molecule can use a different—or multiple—outbound IPs. Firewall changes can take several minutes; restarting PostgreSQL is unnecessary.
4. Test from the same Boomi runtime host with psql using sslmode=require. If that succeeds, the Azure network and credentials are fine and the remaining issue is the Boomi connection/driver configuration.
5. If you switch to verify-full, use the Azure server FQDN and ensure the current Azure root CAs are in the Atom’s Java trust store. Do not disable require_secure_transport; pg_hba.conf is not customer-editable on Flexible Server.

References: Microsoft JDBC example, TLS troubleshooting, and firewall behavior.