Add SSL/TLS support for Postgres connection string #3410
Merged
+1
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Upgrade pg-connection-string to 2.1.0 Fixes knex#852
|
I released pg-connection-string v2.1.0 which fixes the issues with ssl connection string. I tested this on my local fork. |
|
Thanks! |
woyuen
added a commit
to stelace/stelace
that referenced
this pull request
Jul 30, 2020
Some database providers only accepts requests with SSL enabled (e.g. Timescale Cloud). We support the following SSL options: ssl, cert, key, ca Those options will map from Knex.js to the library https://github.com/iceddev/pg-connection-string thanks to the Knex.js PR knex/knex#3410 Please be careful when configuring SSL connection. Passing key value into cert or inversely can trigger an uncaught exception and even `process.on('uncaughtException', fn)` cannot catch it.
woyuen
added a commit
to stelace/stelace
that referenced
this pull request
Aug 14, 2020
Some database providers only accepts requests with SSL enabled (e.g. Timescale Cloud). We support the following SSL options: ssl, cert, key, ca Those options will map from Knex.js to the library https://github.com/iceddev/pg-connection-string thanks to the Knex.js PR knex/knex#3410 Please be careful when configuring SSL connection. Passing key value into cert or inversely can trigger an uncaught exception and even `process.on('uncaughtException', fn)` cannot catch it.
woyuen
added a commit
to stelace/stelace
that referenced
this pull request
Aug 15, 2020
Some database providers only accepts requests with SSL enabled (e.g. Timescale Cloud). We support the following SSL options: ssl, cert, key, ca Those options will map from Knex.js to the library https://github.com/iceddev/pg-connection-string thanks to the Knex.js PR knex/knex#3410 Please be careful when configuring SSL connection. Passing key value into cert or inversely can trigger an uncaught exception and even `process.on('uncaughtException', fn)` cannot catch it. * docs: add instructions to configure SSL for production * refactor: merge Docker PostgreSQL images to keep only SSL one * test: use multi-domains certificate for local and CircleCI environments. Previously, test was failing with a single-domain certificate. SSL certificate was rejected for CircleCI as the host didn't match the certificate information (localhost). For tests, we used a self-signed multi-domains certificate to check database SSL connections. However generating a self-signed multi-domain certificate isn't enough for Node.js, as it will reject it because it is self-signed. To overcome this, we have to sign it with another root certificate (that can be self-signed). For Knex connection configuration, we need to provide the two certificates as `sslcert` and `sslca` properties. In real world usage, you may only need to specify one of them.
This was referenced Mar 15, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #852