BUG #17216: No Password Provided Error - uncaught exception

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: cliffsizer(at)gmail(dot)com
Subject: BUG #17216: No Password Provided Error - uncaught exception
Date: 2021-10-06 08:00:00
Message-ID: 17216-fa0d1504d9dd5b7c@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-jdbc

The following bug has been logged on the website:

Bug reference: 17216
Logged by: cliff sizer
Email address: cliffsizer(at)gmail(dot)com
PostgreSQL version: 14.0
Operating system: Debian 14.0-1.pgdg110+1 on x86_64-pc-linux-gnu
Description:

Using connecting to the pg database 14.0 using jdbc (driver 42.2.24) 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"

The password specific exception is expected rather than the generic message.
According to the release notes the following new feature has been
implemented:

E.1.3.1.8. Authentication - Allow passwords of an arbitrary length (Tom
Lane, Nathan Bossart)

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Dimitri Fontaine 2021-10-06 08:22:08 pg_replication_slot_advance xmin handling when active slot becomes inactive
Previous Message Peter Geoghegan 2021-10-06 06:21:00 Re: BUG #17212: pg_amcheck fails on checking temporary relations

Browse pgsql-jdbc by date

  From Date Subject
Next Message Pierre Brunel 2021-10-06 09:11:13 [Compatibilty][PSQL 13][JDBC 9.1-902] Novice tries to know compatibility issues.
Previous Message Dave Cramer 2021-10-05 14:57:24 [pgjdbc/pgjdbc] daeea3: fix spacing on GSS_ENC_MODE (#2280)