From: Tom Lane <tgl@sss.pgh.pa.us>
To: Agil Azimov <agil.azimov@gmail.com>
cc: pgsql-novice@lists.postgresql.org
Subject: Re: Password settings requirements
In-reply-to: 
 <CAEQStStkY7Hg-MhUnfbn1wMQGzM88uSQ=bLs3BPxGn_WCOmBjA@mail.gmail.com>
References: 
 <CAEQStStkY7Hg-MhUnfbn1wMQGzM88uSQ=bLs3BPxGn_WCOmBjA@mail.gmail.com>
Comments: In-reply-to Agil Azimov <agil.azimov@gmail.com>
	message dated "Tue, 12 Oct 2021 19:00:17 +0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <577836.1634054018.1@sss.pgh.pa.us>
Date: Tue, 12 Oct 2021 11:53:38 -0400
Message-ID: <577837.1634054018@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/577837.1634054018%40sss.pgh.pa.us>
Precedence: bulk

Agil Azimov <agil.azimov@gmail.com> writes:
> Need to check the password settings in postgre such as Password minimal
> length, password complexity, password maximal age, password history and
> account lockout threshold.
> I need to set these parameters to make the comply with the best practices

If you're intent on doing things that way, you can set up Postgres
to use PAM authentication, and then the PAM end of things can be
configured with all kinds of options like that.

Personally though, I'd push back on those requirements.  The fundamental
problem with doing anything like that is that you cannot check password
length, complexity, etc without users having to send their cleartext
passwords to the server, which is a much bigger security fail than
anything appearing on your list.  Best practice these days is to use
SCRAM, which never exposes the cleartext password to the server.

			regards, tom lane