From: | Muhammad Imtiaz <imtiaz(dot)m(at)bitnine(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Rama Krishnan <raghuldrag(at)gmail(dot)com>, Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Valid until |
Date: | 2024-05-14 15:52:03 |
Message-ID: | CANwR1ORoTGxdhY38Lne8VtFW7fCv6=0NGCd1t6aP6OYLJA_wFg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi,
What is the outcome of this query for the specified user? Does the database
contain a value in the rolvaliduntil column?
SELECT rolname, rolvaliduntil FROM pg_authid;
Regards,
M.Imtiaz
On Tue, 14 May 2024 at 20:45, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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 | Dimitrios Apostolou | 2024-05-14 16:14:45 | Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions |
Previous Message | Tom Lane | 2024-05-14 15:45:09 | Re: Valid until |