Re: Change authentication error message (patch) - Mailing list pgsql-hackers

From Jeff Janes
Subject Re: Change authentication error message (patch)
Date
Msg-id CAMkU=1z+e6jRegAL-p2gws_6wTqbcUyB6mobKBB376ALtFVG3w@mail.gmail.com
Whole thread Raw
In response to Re: Change authentication error message (patch)  ("Joshua D. Drake" <jd@commandprompt.com>)
Responses Re: Change authentication error message (patch)  (Markus Wanner <markus@bluegap.ch>)
List pgsql-hackers
On Wed, Jun 19, 2013 at 11:55 AM, Joshua D. Drake <jd@commandprompt.com> wrote:

On 06/18/2013 02:25 AM, Markus Wanner wrote:

On 06/16/2013 06:02 PM, Joshua D. Drake wrote:


How about:
"password authentication failed or account expired for user \"%s\""

It's a bit longer, but sounds more like a full sentence, no?

Yes but I don't think it is accurate, what about:

"Authentication failed or password has expired for user \"%s\""

I think we need to keep the first "password".  "Password authentication" is a single thing, it is the authentication method attempted.  It is the password method (which includes MD5) which failed, as opposed to the LDAP method or the Peer method or one of the other methods.

Without this level of explicitness, it might be hard to figure out which row in pg_hba.conf was the one that PostgreSQL glommed onto to use for authentication.  (Although by this argument, I don't know why MD5 doesn't get its own message specific to it, rather than sharing plain password)

Cheers,

Jeff

pgsql-hackers by date:

Previous
From: Claudio Freire
Date:
Subject: Re: Implementing incremental backup
Next
From: Tatsuo Ishii
Date:
Subject: Re: Implementing incremental backup