Skip to content

Commit b39111c

Browse files
Merge pull request #271122 from GennadNY/gennadyk-branch24
Update concepts-networking-ssl-tls.md
2 parents e0bd6a4 + de7a8fb commit b39111c

File tree

1 file changed

+9
-1
lines changed

1 file changed

+9
-1
lines changed

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

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -203,9 +203,17 @@ For other PostgreSQL client users, you can merge two CA certificate files like t
203203
(Root CA2: Microsoft ECC Root Certificate Authority 2017.crt.pem)
204204
-----END CERTIFICATE-----
205205

206+
### Read Replicas with certificate pinning scenarios
207+
208+
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.
209+
Therefore, for clients that use **verify-ca** and **verify-full** sslmode configuration settings, i.e. certificate pinning, is imperative for interrupted connectivity to accept **both** root CA certificates:
210+
* For connectivity to servers deployed to Azure Government cloud regions (US Gov Virginia, US Gov Texas, US Gov Arizona): [DigiCert Global Root G2](https://www.digicert.com/kb/digicert-root-certificates.htm) and [Microsoft RSA Root Certificate Authority 2017](https://www.microsoft.com/pkiops/docs/repository.htm) root CA certificates, as services are migrating from Digicert to Microsoft CA.
211+
* For connectivity to servers deployed to Azure public cloud regions worldwide: [Digicert Global Root CA](https://www.digicert.com/kb/digicert-root-certificates.htm) and [Microsoft RSA Root Certificate Authority 2017](https://www.microsoft.com/pkiops/docs/repository.htm), as services are migrating from Digicert to Microsoft CA.
212+
213+
206214
## Testing SSL\TLS Connectivity
207215

208-
Before trying to access your SSL enabled server from client application, make sure you can get to it via psql. You should see output similar to the following if you have established an SSL connection.
216+
Before trying to access your SSL enabled server from client application, make sure you can get to it via psql. You should see output similar to the following if you established an SSL connection.
209217

210218

211219
*psql (14.5)*

0 commit comments

Comments
 (0)