| From: | Mohammad Abu Ata <MohammadAA(at)leading-point(dot)com> |
|---|---|
| To: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Cc: | 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: | PostgreSQL 17 — Native Password Policy Support |
| Date: | 2026-10-26 09:43:02 |
| Message-ID: | PAXPR03MB785494FD000AAD7C4CA9F9FF96612@PAXPR03MB7854.eurprd03.prod.outlook.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hello PostgreSQL Community,
We are evaluating PostgreSQL 17 for enterprise use. Could you please confirm whether PostgreSQL provides built-in password policy enforcement without third-party extensions?
Specifically, we need to know whether PostgreSQL natively supports:
- Password complexity and minimum length
- Password expiration
- Password history and prevention of password reuse
- Account lockout after repeated failed login attempts
We are aware of the `passwordcheck` module. Does it provide these capabilities, or are additional extensions or external authentication systems required?
Thank you for your clarification.
Best Regards,
Mohammad Abuata
Senior Software Engineer
Leading Point Software
90, Wasfi At-Tall Street, Amman
T: +96265604808<tel:+96265604808>
M: +962797639855<tel:+962797639855>
M: +96879101447<tel:+962797639855>
www.leading-point.com<https://urldefense.com/v3/__http://www.leading-point.com/__;!!GiDqg7uCaixV!ShbeL6Ho5P9W8jo2ueG-2mCc9iVLOUp8M1Ljk2qqGFmjUnl8fcND7MK63ASYPFvT1h2TQhbO-5z_RWQ0v2jVFk7Z4NES$>
[Facebook icon]<https://urldefense.com/v3/__https://www.facebook.com/LeadingPoint/__;!!GiDqg7uCaixV!ShbeL6Ho5P9W8jo2ueG-2mCc9iVLOUp8M1Ljk2qqGFmjUnl8fcND7MK63ASYPFvT1h2TQhbO-5z_RWQ0v2jVFj2DmDH1$> [LinkedIn icon] <https://urldefense.com/v3/__https://www.linkedin.com/company/leading-point/__;!!GiDqg7uCaixV!ShbeL6Ho5P9W8jo2ueG-2mCc9iVLOUp8M1Ljk2qqGFmjUnl8fcND7MK63ASYPFvT1h2TQhbO-5z_RWQ0v2jVFhbqOIfe$> [Twitter icon] <https://urldefense.com/v3/__https://twitter.com/leadingpointcom__;!!GiDqg7uCaixV!ShbeL6Ho5P9W8jo2ueG-2mCc9iVLOUp8M1Ljk2qqGFmjUnl8fcND7MK63ASYPFvT1h2TQhbO-5z_RWQ0v2jVFp8bMaYA$> [instagram icon] <https://urldefense.com/v3/__https://www.instagram.com/leadingpoint/__;!!GiDqg7uCaixV!ShbeL6Ho5P9W8jo2ueG-2mCc9iVLOUp8M1Ljk2qqGFmjUnl8fcND7MK63ASYPFvT1h2TQhbO-5z_RWQ0v2jVFmdXbKFt$>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | KENAN ÇİFTÇİ | 2026-10-26 10:26:59 | Re: PostgreSQL 17 — Native Password Policy Support |
| Previous Message | Yashwanth | 2026-10-26 08:24:54 | Query: Windows GUI Installer locale selection (English_India.1252 vs en-IN) and risk of silent index corruption when datcollversion is blank |