HOW TO
It is important to note that, although general PostgreSQL documentation often recommends specifying the sslmode parameter, such as "require", "verify-ca", or "verify-full" in client connection strings, this is neither required nor supported when connecting from ArcGIS client software. See the following references:
Based on observed behavior, ArcGIS clients implicitly attempt to establish secure connections using SSL when communicating with cloud-hosted PostgreSQL databases.
To validate that encryption is being used, the following SQL query can be executed via pgAdmin or any SQL client using credentials with appropriate privileges:
SELECT a.datname, a.usename, a.client_addr, s.ssl, s.version, s.cipher FROM pg_stat_activity a LEFT JOIN pg_stat_ssl s ON a.pid = s.pid WHERE a.state = 'active';
The ssl field in the results indicate whether each connection is encrypted. The client_addr field shows the IP addresses of connected clients. In this context, it is expected that the IPs correspond to ArcGIS Pro and ArcGIS Enterprise Server clients.
Note that LEFT JOIN instead of JOIN ensures that all active sessions are included, even if they don’t use SSL, that is, s.ssl will be NULL for non-encrypted connections.
Depending on the deployment of Postgress EGDB there are various ways to configure encrypted communication.
Article ID: 000038744
Get help from ArcGIS experts
Start chatting now