Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tCxfd-00Eob5-2w for pgsql-general@arkaria.postgresql.org; Mon, 18 Nov 2024 09:03:44 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tCxfa-003oWM-GS for pgsql-general@arkaria.postgresql.org; Mon, 18 Nov 2024 09:03:43 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tCxfa-003oWC-5r for pgsql-general@lists.postgresql.org; Mon, 18 Nov 2024 09:03:42 +0000 Received: from mail-il1-x12f.google.com ([2607:f8b0:4864:20::12f]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tCxfY-002XvR-7m for pgsql-general@lists.postgresql.org; Mon, 18 Nov 2024 09:03:42 +0000 Received: by mail-il1-x12f.google.com with SMTP id e9e14a558f8ab-3a75c365679so530005ab.0 for ; Mon, 18 Nov 2024 01:03:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1731920620; x=1732525420; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=m52JHIahpegtfboNuuY4Fq/KSVApIC5pkEFj6wsY2mU=; b=CUdzIKGfCLt3wW0W8WfEX68mRDS7qbh56sR7FXtIQKwC5Ga3iH9VP9tTBxOeLMfOqo 0tt+OKWPiIGsmksWprt0DgufoIICvp7Kmsm6LyHHCPgldBhk9SMu12aAhxDYrAbWhBzN xVVVkHAI8gbcaIvma0kFXSZoH6a3+aqQRkC49k161F+JS5uXnji9qycNC+QtSZcvovcI 4yijipSNWyUD0klUbYzwIlY3VAxt4E8cIlKvDOH1JoyH6U15ZogrWVQoYl2eY+XT0o4J K1v5PBYjjG9EI2nshHwHGVkc6k6u1w8fMdlrak7zFnM3JUmUZg8WIExQUTS/hMohErTN EobQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1731920620; x=1732525420; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=m52JHIahpegtfboNuuY4Fq/KSVApIC5pkEFj6wsY2mU=; b=XOitLomiiaCbQmJRNi0nMc2yEIzlC34PnfPlmKA7qkur9WYAlJa+LPSgZ764Yq9c7F gkijuwMYOSQXDChamid0cD8OLc+tDom3+aRc72EYz7qn2QdnlZfDisowYYUvBCW1fQjG hh4x0xdB8083g8KZNAY0NU9Pu0YEbRJgIGtX9MZe2eE/oWYC8Ia7qh+JVHbdQFs8fySh +ePxVTdFSR37AUhJM0BF7amPVBWa1rK3o3+UTU6QtWMbN/pb0YvTq5Eo3eamXE3balFL yVVBERBSZF8a9PTnUV55W32mj0PPZLv0DptYYMMsjYUU7Y7qg6f94ZQPpbWQB6YaRkev /0Gw== X-Gm-Message-State: AOJu0YwS5u3xwbVNlEwLHUwOU2f2i//hxFVzgXARChk/eldcIMoEzIwZ YrgpyECYyI160/9t0a7Fp5Oelwt7Rkd+Zbg01ZyEsVEsCYB+v9Fejv+nnlLnVAe4k7hE5CMIZ9W L5N8nvCNz5jcRTkXce0cdVga5jaMk/A== X-Google-Smtp-Source: AGHT+IGmg+KJM1HJz8MCrMPeALz46Emsd1uAtEmYCNO5r0kUQito9pjmVAaZJ31xhtF0IacQXMG3Mc3JOtGp5ZWiVVc= X-Received: by 2002:a05:6602:13c1:b0:82a:a4f0:c95e with SMTP id ca18e2360f4ac-83e6c187888mr281484839f.5.1731920619652; Mon, 18 Nov 2024 01:03:39 -0800 (PST) MIME-Version: 1.0 From: =?UTF-8?B?5by15a6455GL?= Date: Mon, 18 Nov 2024 17:03:28 +0800 Message-ID: Subject: Re : Credcheck extension To: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000504f8c06272c312a" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000504f8c06272c312a Content-Type: text/plain; charset="UTF-8" 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! --000000000000504f8c06272c312a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello!=C2=A0
=C2=A0 I would like to inquire abo= ut the installation of the credcheck third-party package to support passwor= d complexity and expiration date, etc., when setting up open-source Postgre= SQL. I am using the credcheck--2.8.0.sql version from GitHub. After complet= ing the setup, I encountered the following issue: when an account exceeds t= he configured number of incorrect login attempts, it gets locked. The comma= nd SELECT * FROM pg_banned_role; should display the columns roleid, failure= _count, and banned_date, and the view is working properly and shows the inf= ormation. 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!
--000000000000504f8c06272c312a--