Jaspersoft report throws errors with no pg_hba.conf

Products

• Clarity PPM On Premise

Issue/Introduction

Post migration to 16.3.3 running on PostgreSQL DB, Jaspersoft report navigations both directly and via channels are failing with error stack:

CIRCULAR REFERENCE: org.postgresql.util.PSQLException: FATAL: no pg_hba.conf entry for host "xxx.xx.xxx.xx" user "clarity", database "clarity", no encryption]

Caused by: org.postgresql.util.PSQLException: FATAL: no pg_hba.conf entry for host "xxx.xx.xxx.xx", user "ppm_jaspersoft", database

 

Note: Clarity, DWH and Jaspersoft schemas on the same DB. 

 

Environment

Clarity 16.3.3 with PostgreSQL 16.4

Cause

This error message FATAL: no pg_hba.conf entry for host "IP Address", user "clarity", database "clarity", no encryption (and the similar one for ppm_jaspersoft) indicates that your PostgreSQL database server is rejecting connections from the Clarity PPM application server IP address

Resolution

Edit the pg_hba.conf file, typically located at common locations (Linux:/var/lib/postgresql/<version>/main/pg_hba.conf or /etc/postgresql/<version>/main/pg_hba.conf or Windows: C:\Program Files\PostgreSQL\<version>\data\pg_hba.conf)

• To allow remote connections from all servers (i.e., all IPv4 addresses), add the following line:
  host all all 0.0.0.0/0 md5
• Alternatively, to allow connections from a specific IP address (e.g., 198.51.100.1), add:host all all 198.51.100.1/32 md5
  (Use your Clarity server's specific IP address if you need to restrict access to it.)

 

Additional Information

Reference: pg_hba.config