Re: BUG #16672: Postgres user passwords are corrupted during migration - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #16672: Postgres user passwords are corrupted during migration
Date
Msg-id 3643196.1602724051@sss.pgh.pa.us
Whole thread Raw
In response to BUG #16672: Postgres user passwords are corrupted during migration  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
"akada shigeki" <zz5s-akd@asahi-net.or.jp> writes:
> solved.
> I was able to restore by changing SCRAM-SHA-256 in HBA.Conf to MD5.
> Does this mean that PSQL doesn't support SHA-256 encryption?

No, it means if you want to use SCRAM authentication then you need the
password that's stored in pg_authid to be hashed with SCRAM.  The password
you carried forward from v12 evidently isn't.  (Again, look into pg_authid
to confirm that.)

Do this, in either v12 or v13, to update the password:

set password_encryption to "scram-sha-256";
alter user postgres with password 'clear text password here';

The system cannot do this for you because there's no way to recover
the cleartext password from the md5 hash.

            regards, tom lane



pgsql-bugs by date:

Previous
From: "akada shigeki"
Date:
Subject: RE: BUG #16672: Postgres user passwords are corrupted during migration
Next
From: Thomas Munro
Date:
Subject: Re: BUG #16663: DROP INDEX did not free up disk space: idle connection hold file marked as deleted