| From: | "Brett Maton" <matonb(at)ltresources(dot)co(dot)uk> |
|---|---|
| To: | <pgadmin-support(at)postgresql(dot)org> |
| Subject: | Password Expiry |
| Date: | 2013-04-10 11:31:35 |
| Message-ID: | 003a01ce35de$f69a4400$e3cecc00$@ltresources.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
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.
Best regards,
Brett
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2013-04-10 12:03:12 | Re: Password Expiry |
| Previous Message | ldrlj1 | 2013-04-10 11:15:04 | Re: PGAdmin Release 1.16.2 |