From: Tom Lane <tgl@sss.pgh.pa.us>
To: cliffsizer@gmail.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17216: No Password Provided Error - uncaught exception
In-reply-to: <17216-fa0d1504d9dd5b7c@postgresql.org>
References: <17216-fa0d1504d9dd5b7c@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Wed, 06 Oct 2021 08:00:00 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4139743.1633529791.1@sss.pgh.pa.us>
Date: Wed, 06 Oct 2021 10:16:31 -0400
Message-ID: <4139744.1633529791@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/4139744.1633529791%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> Using connecting to the pg database 14.0 using jdbc (driver 42.2.24)

How old is that JDBC driver?

> and no
> password (empty) is specified the following error message is returned
> "Something unusual has occurred to cause the driver to fail. Please report
> this exception." In previous versions (13.4) the password specific error
> message is returned "The server requested password-based authentication, but
> no password was provided"

I suspect the server is asking for a SCRAM-encrypted password and the
JDBC driver doesn't recognize that as a valid authentication request.
If you don't want to update the driver, don't use SCRAM passwords.
(Note that SCRAM password encryption is on by default in v14;
see password_encryption setting.)

			regards, tom lane