From: | Wim Bertels <wim(dot)bertels(at)ucll(dot)be> |
---|---|
To: | "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Unexpected authentication behaviour |
Date: | 2024-08-27 08:49:32 |
Message-ID: | 1b95a3c28d448c7b4b538937f2e7d7facb1930b1.camel@ucll.be |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hello Izum
in my memory,
this is the fallback behaviour to a safer auth method (from md5 to
scram), the other way around it doesn't work;
correct me if i'm wrong, should be in the documentation
hth,
Wim
Domen Šetar schreef op di 27-08-2024 om 08:00 [+0000]:
> Hi Admins,
>
> I have strange issue that I can't explain to myself:
>
> I want to use scram-sha-256 authentication on postgresql 16.
> Parameter password_encryption is set to scram-sha-256. I defined a
> user with scram-sha-256 encoded password.
> My pg_hba.conf have following lines:
>
> # TYPE DATABASE USER ADDRESS
> METHOD
> local all
> all peer
> host all all
> samenet md5
>
> Even though there is defined md5 authentication method for remote
> logins in pg_hba.conf I can make remote login to my postgresql server
> which is unexpected behaviour of postgresql.
> What did I miss?
>
> Best regards!
> izum
> Domen Šetar
> Computer Systems Support
> IZUM – Institute of Information Science| Prešernova ulica 17 | 2000
> Maribor |Slovenia
> T: +386 2 25 20 339| M: +386 41 676
> 342|www.izum.si|domen(dot)setar(at)izum(dot)si
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Ram Pratap Maurya | 2024-08-27 08:50:36 | After DB upgrade from PG13 to PG15 showing error |
Previous Message | Domen Šetar | 2024-08-27 08:00:15 | Unexpected authentication behaviour |