Skip to content

Commit 2c2a7b8

Browse files
Merge pull request #220483 from jonels-msft/cdbpg-tls-cert
Azure Cosmos DB for PostgreSQL uses a new root CA
2 parents 45aceca + 3c8ccf7 commit 2c2a7b8

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/cosmos-db/postgresql/howto-ssl-connection-security.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.service: cosmos-db
77
ms.subservice: postgresql
88
ms.custom: ignite-2022
99
ms.topic: conceptual
10-
ms.date: 07/16/2020
10+
ms.date: 12/06/2022
1111
---
1212
# Configure TLS in Azure Cosmos DB for PostgreSQL
1313

@@ -23,26 +23,26 @@ The TLS parameters `ssl` and `sslmode` vary based on the capabilities of the con
2323
Some application frameworks don't enable TLS by default for PostgreSQL connections. However, without a secure connection, an application can't connect to the coordinator node. Consult your application's documentation to learn how to enable TLS connections.
2424

2525
## Applications that require certificate verification for TLS connectivity
26-
In some cases, applications require a local certificate file generated from a trusted Certificate Authority (CA) certificate file (.cer) to connect securely. The certificate to connect to an Azure Cosmos DB for PostgreSQL is located at https://cacerts.digicert.com/DigiCertGlobalRootCA.crt.pem. Download the certificate file and save it to your preferred location.
26+
In some cases, applications require a local certificate file generated from a trusted Certificate Authority (CA) certificate file (.cer) to connect securely. The certificate to connect to an Azure Cosmos DB for PostgreSQL is located at https://cacerts.digicert.com/DigiCertGlobalRootG2.crt.pem Download the certificate file and save it to your preferred location.
2727

2828
> [!NOTE]
2929
>
3030
> To check the certificate's authenticity, you can verify its SHA-256
3131
> fingerprint using the OpenSSL command line tool:
3232
>
3333
> ```sh
34-
> openssl x509 -in DigiCertGlobalRootCA.crt.pem -noout -sha256 -fingerprint
34+
> openssl x509 -in DigiCertGlobalRootG2.crt.pem -noout -sha256 -fingerprint
3535
>
3636
> # should output:
37-
> # 43:48:A0:E9:44:4C:78:CB:26:5E:05:8D:5E:89:44:B4:D8:4F:96:62:BD:26:DB:25:7F:89:34:A4:43:C7:01:61
37+
> # CB:3C:CB:B7:60:31:E5:E0:13:8F:8D:D3:9A:23:F9:DE:47:FF:C3:5E:43:C1:14:4C:EA:27:D4:6A:5A:B1:CB:5F
3838
> ```
3939
4040
### Connect using psql
4141
The following example shows how to connect to your coordinator node using the psql command-line utility. Use the `sslmode=verify-full` connection string setting to enforce TLS certificate verification. Pass the local certificate file path to the `sslrootcert` parameter.
4242
4343
Below is an example of the psql connection string:
4444
```
45-
psql "sslmode=verify-full sslrootcert=DigiCertGlobalRootCA.crt.pem host=mydemoserver.postgres.database.azure.com dbname=citus user=citus password=your_pass"
45+
psql "sslmode=verify-full sslrootcert=DigiCertGlobalRootG2.crt.pem host=mydemoserver.postgres.database.azure.com dbname=citus user=citus password=your_pass"
4646
```
4747
> [!TIP]
4848
> Confirm that the value passed to `sslrootcert` matches the file path for the certificate you saved.

0 commit comments

Comments
 (0)