Hi
On Wed, Apr 10, 2013 at 12:31 PM, Brett Maton <mat...@ltresources.co.uk> wrote:
> pgAdmin v 1.16.1
>
> Windows 7 x64
>
>
>
> PostgreSQL v9.4.2
>
> CentOS 6.4
>
>
>
> pgAdmin by default when editing a user’s account settings seems to set
> Account Validity to ‘1969-12-31 00:00:00+01’ if the role is defined as valid
> until infinity.
>
> This results in the user not being able to login, and only receiving a
> password authentication failed error message (Account Expired would be more
> helpful, but that’s for Postgres ;)).
>
>
>
> An example would be adding a user to a group role via the Role membership
> tab, and never actually opening the Definition tab.
>
> You’d be blissfully unaware that Password validity had been changed.
This has been fixed already for future releases:
commit 265143d8134a5d191ad6db1162a9408f23c185c7
Author: Dave Page <dp...@pgadmin.org>
Date: Wed Feb 6 15:24:50 2013 +0000
Fix expiry date handling for users.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-support
