| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Hemil Ruparel <hemilruparel2002(at)gmail(dot)com> |
| 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:36:54 |
| Message-ID: | 704984.1606491414@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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 | Hemil Ruparel | 2020-11-27 15:44:57 | Re: How to debug authentication issues in Postgres |
| Previous Message | Gustavsson Mikael | 2020-11-27 15:30:23 | SV: Problem with pg_notify / listen |