| From: | Teja Jakkidi <teja(dot)jakkidi05(at)gmail(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Credcheck max_auth_failure |
| Date: | 2025-01-09 06:19:53 |
| Message-ID: | 131956F0-B580-465D-91B2-C52D9E54EA05@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Thank you, David.
Regards,
J. Teja.
On Jan 8, 2025, at 9:32 PM, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
On Wednesday, January 8, 2025, Teja Jakkidi <teja(dot)jakkidi05(at)gmail(dot)com> wrote:
1. The parameter is working as expected on primary and banning the id in the 3rd attempt with wrong password.
However, I am not able to figure out how to get the banned user back to working. Restarting instance will get the banned user working but restarting whole instance to activate one user is not a feasible solution.
You should read its docs. It discusses this.
https://github.com/HexaCluster/credcheck?tab=readme-ov-file#authentication-failure-ban
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Samuel VISCAPI | 2025-01-09 10:08:24 | 2nd PostgreSQL server in WAL shipping cluster fails to start |
| Previous Message | David G. Johnston | 2025-01-09 05:32:20 | Re: Credcheck max_auth_failure |