error: connection requires a valid client certificate with pg-pool 3.2.2

[eyalcohen]

With configuration as follows:

const postgresConfig = {
  ...
  ssl: {
    rejectUnauthorized: false,
    ca: env.serverca,
    key: env.clientkey,
    cert: env.clientcert
  }
  ...
}

I get an error: connection requires a valid client certificate

My configuration worked fine with pg 8.4.1 / pg-pool 3.2.1 and breaks on pg 8.4.1 / pg-pool 3.2.2.

I believe commit 80c500f is the source of my issue, but perhaps there is a more correct way to pass the certificates now.

[brianc]

This should be fixed on the version I released today! Please let me know if its still not working....we have test coverage for this now.

…

On Tue, Nov 10, 2020 at 12:23 AM Eyal Cohen ***@***.***> wrote: With configuration as follows: const postgresConfig = { ... ssl: { rejectUnauthorized: false, ca: env.serverca, key: env.clientkey, cert: env.clientcert } ... } I get an error: connection requires a valid client certificate My configuration worked fine with pg 8.4.1 / pg-pool 3.2.1 and breaks on pg 8.4.1 / pg-pool 3.2.2. I believe commit 80c500f <80c500f> is the source of my issue, but perhaps there is a more correct way to pass the certificates now. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#2405>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAMHIIAUWRE7FPUU4IR663SPDL5ZANCNFSM4TQH37RA> .

[charmander]

Duplicate of #2392

[domosapien]

This was still broken as of yesterday. It seems like pg-pool@3.2.2 is breaking it. See vitaly-t/pg-promise#764 (comment)

[charmander]

@domosapien Did you upgrade to pg 8.5.1?

[domosapien]

@domosapien Did you upgrade to pg 8.5.1?

@charmander I have not. Looking at the diff between 8.5.0 and 8.5.1, it doesn't look like anything really would affect what I'm seeing, or what others have reported in that thread. I can attempt that version soon, but I don't have high hopes.

[charmander]

@domosapien 8.5.0 should be fine. Are you using pg-promise? pg-promise still depends on 8.4.1.

[domosapien]

@charmander ahh, I guess the changes in 8.5.0 fixes it (tested with a beta version of pg-promise that updates the lib version). I thought it was an issue here too due to pg-pool requiring a set version in the testing we had done. Thanks for the support.