BUG #15035: scram-sha-256 blocks all logins
| От | David G. Johnston |
|---|---|
| Тема | BUG #15035: scram-sha-256 blocks all logins |
| Дата | |
| Msg-id | CAKFQuwbthtxsDcf1YqYO4JiC3KeoejeuJsfWk6pFaSpauHAoaA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: BUG #15035: scram-sha-256 blocks all logins (Meirav Rath <meirav.rath@imperva.com>) |
| Ответы |
RE: BUG #15035: scram-sha-256 blocks all logins
|
| Список | pgsql-bugs |
On Monday, January 29, 2018, Meirav Rath <meirav.rath@imperva.com> wrote:
I set up the password hashing method to scram and now no one can login to the server and that's not a bug??
If we understand the problem correctly, no, it's not a bug: changing the password type setting after deployment requires some work to change pre-existing roles. It is not possible for the server to do it for you, the passwords being encrypted.
I think the short answer is to setup pg_hba.conf so you can get a superuser login without a password (peer or trust) and then alter the superuser password and create/alter any users you want with new password in scram format.
David J.
В списке pgsql-bugs по дате отправления: