From: Stephen Frost <sfrost@snowman.net>
To: Daulat <daulat.dba@gmail.com>
Cc: pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: Password authorization
Date: Fri, 21 Jan 2022 14:50:07 -0500
Message-ID: <20220121195007.GI10577@tamriel.snowman.net> (raw)
In-Reply-To: <CALfOM6KtjqpO5pYgmpUmDScJMeftv9r509HfYLo2b8gebviL3g@mail.gmail.com>
References: <CALfOM6KtjqpO5pYgmpUmDScJMeftv9r509HfYLo2b8gebviL3g@mail.gmail.com>
Greetings,
* Daulat (daulat.dba@gmail.com) wrote:
> Is there any alternative in postgres to manage the user password
> authorisation?
> What about LDAP with respect to this approach?
PostgreSQL supports GSSAPI / Kerberos, which is a much better approach
in Active Directory and other environments where Kerberos is deployed.
Using LDAP exposes the user's password to the database server and
therefore isn't secure and should be strongly discouraged.
You can certainly have applications authenticate to PostgreSQL using
Kerberos too with very little overhead (unlike PG's LDAP authentication
option, which makes a synchronous call out to the LDAP server on each
and every login).
Thanks,
Stephen
Attachments:
signature.asc (application/pgp-signature, 818B) download
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: sfrost@snowman.net, daulat.dba@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: Password authorization
In-Reply-To: <20220121195007.GI10577@tamriel.snowman.net>
* 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