MIME-Version: 1.0
References: <CAFsaSDg3oCwP=Oq7Ej7=PLLHy6_5sUn65LwrQFxw0MvEwm=uAA@mail.gmail.com>
In-Reply-To: <CAFsaSDg3oCwP=Oq7Ej7=PLLHy6_5sUn65LwrQFxw0MvEwm=uAA@mail.gmail.com>
From: Julien Rouhaud <rjuju123@gmail.com>
Date: Mon, 18 Nov 2024 17:36:13 +0800
Message-ID: <CAOBaU_YVmXtv1AtunhmmOPb1yCsvBeoeiM2+2ZgL=ZsKZfrjgg@mail.gmail.com>
Subject: Re: Re : Credcheck extension
To: =?UTF-8?B?5by15a6455GL?= <kenny020307@gmail.com>
Cc: pgsql-general@lists.postgresql.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://www.postgresql.org/message-id/CAOBaU_YVmXtv1AtunhmmOPb1yCsvBeoeiM2%2B2ZgL%3DZsKZfrjgg%40mail.gmail.com>
Precedence: bulk

Hi,

On Mon, Nov 18, 2024 at 5:03=E2=80=AFPM =E5=BC=B5=E5=AE=B8=E7=91=8B <kenny0=
20307@gmail.com> wrote:
>
> Hello!
>   I would like to inquire about the installation of the credcheck third-p=
arty package to support password complexity and expiration date, etc., when=
 setting up open-source PostgreSQL. I am using the credcheck--2.8.0.sql ver=
sion from GitHub. After completing the setup, I encountered the following i=
ssue: when an account exceeds the configured number of incorrect login atte=
mpts, it gets locked. The command SELECT * FROM pg_banned_role; should disp=
lay the columns roleid, failure_count, and banned_date, and the view is wor=
king properly and shows the information. However, according to the example,=
 the roleid does not correctly display the corresponding oid for the accoun=
t with failed login attempts. I would like to ask if there is a solution fo=
r this issue. Thank you!

I did a quick test locally and as far as I can see it seems to work as expe=
cted:

$ psql -U bob postgres
Password for user bob:
psql: error: connection to server at "127.0.0.1", port 11035 failed:
FATAL:  password authentication failed for user "bob"

$ psql -U postgres -c "SELECT roleid::regrole, * from pg_banned_role"
 roleid | roleid | failure_count | banned_date
--------+--------+---------------+-------------
 bob    | 750815 |             1 | <NULL>
(1 row)

If you don't get a similar behavior you should raise an issue to the
author directly on the extension's github repo.