Feedback-ID: i76984098:Fastmail
Message-ID: <a24b9322-bb7f-4a2d-a85c-994956eaf491@aklaver.com>
Date: Tue, 29 Oct 2024 09:06:12 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Compatibility Issues with Npgsql and .NET Framework 3.5 after
 Upgrading to PostgreSQL 16.3
To: Daniel Gustafsson <daniel@yesql.se>, =?UTF-8?B?6aasIOmosOmjmw==?=
 <ma-tengfei@nec.cn>
Cc: "pgsql-general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>
References: <BJSPR01MB04989313C380D79F1A0EE0A5E24B2@BJSPR01MB0498.CHNPR01.prod.partner.outlook.cn>
 <DBE429A3-B64F-43AB-AA25-FC2A0CFE47F3@yesql.se>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <DBE429A3-B64F-43AB-AA25-FC2A0CFE47F3@yesql.se>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://www.postgresql.org/message-id/a24b9322-bb7f-4a2d-a85c-994956eaf491%40aklaver.com>
Precedence: bulk

On 10/29/24 04:01, Daniel Gustafsson wrote:
>> On 29 Oct 2024, at 04:25, 馬　騰飛 <ma-tengfei@nec.cn> wrote:
>>
>> Thank you very much for your reply.
>> However, after installing PostgreSQL 16.4, our server still encounters the following error when connecting to the database, just like with version 16.3:
>> “Only AuthenticationClearTextPassword and AuthenticationMD5Password supported for now. Received: 10”.
>> Could you please advise how to resolve this error? Should we also update Npgsql? If Npgsql needs to be updated, to which version should we update it?
> 
> I don't know the first thing about Npgsql so I can't offer any advice, but it
> sounds like the problems is that the server wants to use SCRAM passwords and
> your version of npgsql only support cleartext and md5.  Changing the METHOD in
> pg_hba.conf to md5 could fix the immediate problem perhaps but upgrading to a
> version that support SCRAM seems the most appropriate (especially since md5
> passwords are likely going away soon).

Potential issue with above per:

https://www.postgresql.org/docs/current/auth-password.html

"To ease transition from the md5 method to the newer SCRAM method, if 
md5 is specified as a method in pg_hba.conf but the user's password on 
the server is encrypted for SCRAM (see below), then SCRAM-based 
authentication will automatically be chosen instead."

Therefore a roles password could still be in SCRAM. You would need to 
change the actual passwords also.


According to the issue below Npgsql supports SCRAM:

https://github.com/npgsql/npgsql/issues/5593

Which translates into Npgsql 3.2.7:

https://github.com/npgsql/npgsql/releases/tag/v3.2.7

> 
> --
> Daniel Gustafsson
> 
> 
> 

-- 
Adrian Klaver
adrian.klaver@aklaver.com