Message-ID: <f0455f10526a0463c9e99fc803b6e5ebfd518894.camel@cybertec.at>
Subject: Re: Password authorization
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Daulat <daulat.dba@gmail.com>, pgsql-admin
	 <pgsql-admin@lists.postgresql.org>
Date: Thu, 20 Jan 2022 15:25:24 +0100
In-Reply-To: 
 <CALfOM6KtjqpO5pYgmpUmDScJMeftv9r509HfYLo2b8gebviL3g@mail.gmail.com>
References: 
	<CALfOM6KtjqpO5pYgmpUmDScJMeftv9r509HfYLo2b8gebviL3g@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.40.4 (3.40.4-2.fc34) 
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: 
 <https://www.postgresql.org/message-id/f0455f10526a0463c9e99fc803b6e5ebfd518894.camel%40cybertec.at>
Precedence: bulk

On Thu, 2022-01-20 at 15:26 +0530, Daulat wrote:
> Do we have any facility for password authorisation in Postgres same as in Oracle?
> In Oracle, a user can change their password based upon the profile setting. What about in Postgres ? 
> 
> Is there any alternative in postgres to manage the user password authorisation? 
> What about LDAP with respect to this approach?
> Please suggest.

It is not quite clear what you mean, but I assume you want password complexity rules,
and you want to force users to change their password after a while.

You cannot do any of that with passwords in the database; the best you can
do is set an expiration time for the user's ability to log in.

With requirements as this, you should look into external password
authentication like Kerberos or LDAP - you'll have to look at that server's
documentation for more.

Yours,
Laurenz Albe
-- 
Cybertec | https://www.cybertec-postgresql.com