Skip to content

Commit 2d1e71a

Browse files
committed
Update concepts-networking-ssl-tls.md
1 parent 2764f96 commit 2d1e71a

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

articles/postgresql/flexible-server/concepts-networking-ssl-tls.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -131,6 +131,11 @@ openssl x509 -in certificate.crt -out certificate.pem -outform PEM
131131

132132
**Detailed information on updating client applications certificate stores with new Root CA certificates has been documented in this [how-to document](../flexible-server/how-to-update-client-certificates-java.md)**.
133133

134+
135+
> [!IMPORTANT]
136+
> Some of the Postgres client libraries, while using **sslmode=verify-full** setting, may experience connection failures with Root CA certificates that are cross-signed with intermediate certificates, resulting in alternate trust paths. In this case, its recommended explicitly specify **sslrootcert** parameter, explained above, or set the PGSSLROOTCERT environment variable to local path where Microsoft RSA Root Certificate Authority 2017 Root CA certificate is placed, from default value of *%APPDATA%\postgresql\root.crt*.
137+
138+
134139
### Read Replicas with certificate pinning scenarios
135140

136141
With Root CA migration to [Microsoft RSA Root Certificate Authority 2017](https://www.microsoft.com/pkiops/docs/repository.htm) it's feasible for newly created replicas to be on a newer Root CA certificate than primary server created earlier.

0 commit comments

Comments
 (0)