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 <br...@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
diff --git a/src/backend/libpq/auth.c b/src/backend/libpq/auth.c
new file mode 100644
index 882dc8f..fa96238
*** a/src/backend/libpq/auth.c
--- b/src/backend/libpq/auth.c
*************** auth_failed(Port *port, int status)
*** 245,251 ****
break;
case uaPassword:
case uaMD5:
! errstr = gettext_noop("password authentication failed for user \"%s\"");
/* We use it to indicate if a .pgpass password failed. */
errcode_return = ERRCODE_INVALID_PASSWORD;
break;
--- 245,251 ----
break;
case uaPassword:
case uaMD5:
! errstr = gettext_noop("password authentication failed for user \"%s\": invalid or expired password");
/* We use it to indicate if a .pgpass password failed. */
errcode_return = ERRCODE_INVALID_PASSWORD;
break;
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
