Re: PostgreSQL 17 — Native Password Policy Support

From: Christophe Pettus <xof(at)thebuild(dot)com>
To: Mohammad Abu Ata <MohammadAA(at)leading-point(dot)com>
Cc: "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>, Abdelrahman Mansour <abdelrahman(dot)mansour(at)stc(dot)com(dot)kw>, Ahmad Y Al Kandari <ahmad(dot)alkandarei(at)stc(dot)com(dot)kw>, Mahmoud Al-Muhtaseb <MahmmudM(at)leading-point(dot)com>
Subject: Re: PostgreSQL 17 — Native Password Policy Support
Date: 2026-10-26 10:50:52
Message-ID: D889D095-175E-4546-9F47-9804B5DBEC31@thebuild.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

> On Oct 26, 2026, at 09:43, Mohammad Abu Ata <MohammadAA(at)leading-point(dot)com> wrote:
>
> We are evaluating PostgreSQL 17 for enterprise use. Could you please confirm whether PostgreSQL provides built-in password policy enforcement without third-party extensions?

The question is a bit more nuanced than "yes" or "no." `passwordcheck` provides basic password complexity checking, but does not provide the other aspects of policy enforcement you are looking for.

As the `passwordcheck` documentation notes, password complexity checking within PostgreSQL's core server is difficult to provide for authentication methods where the password is stored in the database itself, as the client has the option to send over a pre-hashed password.

Again, as the `passwordcheck` documentation notes, if you have security requirements of the type you describe, it's better to use an external password management system such as GSSAPI, rather than store passwords direclty in the database. This also meets a very common requirement for immediate blanket revocation of authorization for a terminated user, rather than having to disable accounts piecemeal across the environment.

PostgreSQL does provide a wide range of authentication mechanisms directly in the core distribution; you can see the full list at:

https://www.postgresql.org/docs/current/client-authentication.html

Best,
-- Christophe

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Mark 2026-10-26 10:52:50 Re: Debugging --- ERROR: function does not exist
Previous Message Mark 2026-10-26 10:49:42 Re: Debugging --- ERROR: function does not exist