| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | 張宸瑋 <kenny020307(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Re : Credcheck extension |
| Date: | 2024-11-18 15:15:30 |
| Message-ID: | bc81b050-b072-4e09-aac6-be57ca4a0df1@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 11/18/24 01:03, 張宸瑋 wrote:
> Hello!
> I would like to inquire about the installation of the credcheck
> third-party package to support password complexity and expiration date,
> etc., when setting up open-source PostgreSQL. I am using the
> credcheck--2.8.0.sql version from GitHub. After completing the setup, I
> encountered the following issue: when an account exceeds the configured
> number of incorrect login attempts, it gets locked. The command SELECT *
> FROM pg_banned_role; should display the columns roleid, failure_count,
> and banned_date, and the view is working properly and shows the
> information. However, according to the example, the roleid does not
> correctly display the corresponding oid for the account with failed
> login attempts. I would like to ask if there is a solution for this
> issue. Thank you!
Have you looked a?:
https://github.com/HexaCluster/credcheck/issues/39
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexandru Lazarev | 2024-11-18 16:11:15 | Re: work_mem RAM Accounting in PostgreSQL |
| Previous Message | Gianni Ceccarelli | 2024-11-18 14:43:07 | Re: Functions and Indexes |