Feature request: support `sslpassphrase` parameter in connection string parsing

Open Beginner friendly
#3,716 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
75/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Quiet
Tech stack
javascript, postgresql
Domain
database

Research direction

Locate the connection-string parsing entry point and inspect how existing SSL-related query parameters are handled. Add support for the example's sslpassphrase parameter so it reaches config.ssl.passphrase, then verify the parsed configuration using the project's existing connection-string tests or test command.

Written by the indexing model from the issue text.

Description

Describe the solution you'd like

Parse the sslpassphrase query parameter and assign it to config.ssl.passphrase, similar to how other SSL-related parameters are handled.

Example

Given the following connection string:
postgres://user:pass@host:5432/db?sslmode=verify-full&sslrootcert=/path/to/ca.crt&sslcert=/path/to/client.crt&sslkey=/path/to/client.key&sslpassphrase=MySecretPass

I'd be happy to submit a PR for this.

Dominant language
JavaScript
Stars
13.2k
Forks
1.4k
Avg merge
6d 15h
Merged PRs (30d)
6

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from brianc/node-postgres

All issues in brianc/node-postgres

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.