From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Daulat <daulat.dba@gmail.com>
To: pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: Password authorization
Date: Thu, 20 Jan 2022 15:25:24 +0100
Message-ID: <f0455f10526a0463c9e99fc803b6e5ebfd518894.camel@cybertec.at> (raw)
In-Reply-To: <CALfOM6KtjqpO5pYgmpUmDScJMeftv9r509HfYLo2b8gebviL3g@mail.gmail.com>
References: <CALfOM6KtjqpO5pYgmpUmDScJMeftv9r509HfYLo2b8gebviL3g@mail.gmail.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: laurenz.albe@cybertec.at, daulat.dba@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: Password authorization
In-Reply-To: <f0455f10526a0463c9e99fc803b6e5ebfd518894.camel@cybertec.at>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox