| From: | Hemil Ruparel <hemilruparel2002(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "Zwettler Markus (OIZ)" <Markus(dot)Zwettler(at)zuerich(dot)ch>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Subject: | Re: How to debug authentication issues in Postgres |
| Date: | 2020-11-27 15:44:57 |
| Message-ID: | CANW1aT9Ne-_ynNisWfQA6Q5exNDt0L6Ocu+aAY=zHEUkMpEGgw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Thanks for the clarification. According to this page,
https://jdbc.postgresql.org/documentation/changelog.html#version_42.2.0,
scram support was added in JDBC driver 42.2.0. I am on 42.2.18. And using
the java code mentioned above, I still get the same error.
On Fri, Nov 27, 2020 at 9:06 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Hemil Ruparel <hemilruparel2002(at)gmail(dot)com> writes:
> > When I try to connect to the database, the log says:
> >> FATAL: password authentication failed for user "user"
> >> DETAIL: Connection matched pg_hba.conf line 88: "host user
> > password 0.0.0.0/0 scram-sha-256"
>
> > So I think the client is using scram-sha-256
>
> No, what that says is that the server is going to insist on scram-sha-256.
> If the client can't handle SCRAM, then a failure would be expected.
>
> regards, tom lane
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-11-27 15:55:13 | Re: How to debug authentication issues in Postgres |
| Previous Message | Tom Lane | 2020-11-27 15:36:54 | Re: How to debug authentication issues in Postgres |