Re: BUG #17216: No Password Provided Error - uncaught exception

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: cliffsizer(at)gmail(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17216: No Password Provided Error - uncaught exception
Date: 2021-10-06 14:16:31
Message-ID: 4139744.1633529791@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-jdbc

PG Bug reporting form <noreply(at)postgresql(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Robert Haas 2021-10-06 14:44:44 Re: Extension relocation vs. schema qualification
Previous Message PG Bug reporting form 2021-10-06 14:09:29 BUG #17217: PANIC: stuck spinlock detected at LockBufHdr, bufmgr.c:4297

Browse pgsql-jdbc by date

  From Date Subject
Next Message Dave Cramer 2021-10-06 16:56:14 [pgjdbc/pgjdbc] ab228e: fix: Github actions were failing due to PostgreSQL...
Previous Message Tom Lane 2021-10-06 13:46:28 Re: [Compatibilty][PSQL 13][JDBC 9.1-902] Novice tries to know compatibility issues.