| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | Rama Krishnan <raghuldrag(at)gmail(dot)com>, Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Valid until |
| Date: | 2024-05-14 15:45:09 |
| Message-ID: | 1102603.1715701509@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> writes:
> On 5/14/24 00:57, Rama Krishnan wrote:
>> I recently set a user's password validity to "2024-05-13", but despite
>> this, the user is still able to connect to the database. Is this a bug,
>> or is the "valid until" parameter just for identification purposes,
>> indicating when the password will expire?
> The VALID UNTIL clause sets a date and time after which the role's
> password is no longer valid. If this clause is omitted the password will
> be valid for all time.
The important point there is that the *password* is not usable after
the specified date. If the user logs in via some non-password-based
authentication method, that's fine (and it's on the infrastructure
of that auth method to enforce whatever restrictions it thinks are
appropriate).
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Muhammad Imtiaz | 2024-05-14 15:52:03 | Re: Valid until |
| Previous Message | Adrian Klaver | 2024-05-14 15:27:02 | Re: Valid until |