From: Tom Lane <tgl@sss.pgh.pa.us>
To: Julien Rouhaud <rjuju123@gmail.com>
cc: Naveed Iftikhar <naveed27c@yahoo.com>,
        "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Subject: Re: While creating a user in PostgreSQL 15 getting ERROR: require a
 VALID UNTIL option
In-reply-to: <vbkut24ppzneayn37ju67sc5yjqmutwcotkilxitbya5hu66me@rnxyxdt7i4nu>
References: 
 <CAFhgWoLAh18RdnqzZuFfZ-i7Zi_Z2iUUD2CwBJKRsYzWA__t+Q@mail.gmail.com>
 <89AA09AC-A627-4EAB-8B0C-0EE184BD56A2@elevated-dev.com>
 <CAFhgWoKb7nFhHteZC9x14t9i7WPvr1UBBuMvBGgtQ=d6-vjNsA@mail.gmail.com>
 <15DE7820-429C-4163-BC59-E7608CF228B8@elevated-dev.com>
 <808751752.1562387.1715492644219@mail.yahoo.com>
 <ioj5zhbgfx5u3mjdnzlsmhoffqma2ch4mqctldeckxpdg2kukx@bsapfasejdth>
 <160028138.1567187.1715493876270@mail.yahoo.com>
 <vbkut24ppzneayn37ju67sc5yjqmutwcotkilxitbya5hu66me@rnxyxdt7i4nu>
Comments: In-reply-to Julien Rouhaud <rjuju123@gmail.com>
	message dated "Sun, 12 May 2024 14:09:40 +0800"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <182421.1715494848.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Sun, 12 May 2024 02:20:48 -0400
Message-ID: <182422.1715494848@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/182422.1715494848%40sss.pgh.pa.us>
Precedence: bulk

Julien Rouhaud <rjuju123@gmail.com> writes:
> On Sun, May 12, 2024 at 06:04:36AM GMT, Naveed Iftikhar wrote:
>> =C2=A0 Thanks, I think previous DBA has created=C2=A0credcheck extensio=
n. How can I remove or bypass or create the user with valid until ..=C2=A0=
 even I provide the valid until but still getting the error.

> You should look at the documentation for the exact syntax to use:
> https://github.com/MigOpsRepos/credcheck

This is pretty rich, because not only is credcheck making up this
valid-until date on its own, but then it's objecting to what it
made up.  'Jan 31 2030' is a perfectly valid date according to
Postgres, and "require a VALID UNTIL option with a date beyond 120
days" is not an error that appears anywhere in core Postgres, even
if we somehow failed to do the implied date arithmetic correctly.

I think your answer is to remove that extension, preferably
with gloves and tongs.

			regards, tom lane