| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | Markus Wanner <markus(at)bluegap(dot)ch>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Change authentication error message (patch) |
| Date: | 2014-01-24 02:52:52 |
| Message-ID: | 20140124025252.GA8993@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jun 19, 2013 at 01:27:39PM -0700, Joshua D. Drake wrote:
>
> On 06/19/2013 01:18 PM, Markus Wanner wrote:
>
> >>"Authentication failed or password has expired for user \"%s\""
> >>
> >>Authentication failed covers any combination of a username/password
> >>being wrong and obviously password expired covers the other.
> >
> >Works for me. Considering the password to be the thing that expires
> >(rather than the account) is probably more accurate as well.
>
> It is also how it is worded in the docs (which is why I used it).
> Patch below.
I have developed the attached patch to fix this problem. Do I need to
say "invalid user or invalid or expired password"?
---------------
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
| Attachment | Content-Type | Size |
|---|---|---|
| auth.diff | text/x-diff | 786 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2014-01-24 03:15:36 | Re: [v9.4] row level security |
| Previous Message | Tomas Vondra | 2014-01-24 02:48:29 | Re: GIN improvements part2: fast scan |