From: Tom Lane <tgl@sss.pgh.pa.us>
To: Adrian Klaver <adrian.klaver@aklaver.com>
cc: Rama Krishnan <raghuldrag@gmail.com>,
        Postgres General <pgsql-general@postgresql.org>
Subject: Re: Valid until
In-reply-to: <7dff9a17-744d-437b-847c-18c161c8a901@aklaver.com>
References: <CAJWX+EOModYYe-LDVP_1zceryEd186u=pcaTE6Sb_9XMtjhWKA@mail.gmail.com> <7dff9a17-744d-437b-847c-18c161c8a901@aklaver.com>
Comments: In-reply-to Adrian Klaver <adrian.klaver@aklaver.com>
	message dated "Tue, 14 May 2024 08:27:02 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1102602.1715701509.1@sss.pgh.pa.us>
Date: Tue, 14 May 2024 11:45:09 -0400
Message-ID: <1102603.1715701509@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/1102603.1715701509%40sss.pgh.pa.us>
Precedence: bulk

Adrian Klaver <adrian.klaver@aklaver.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