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 1tVl4n-00BBmG-3T for pgsql-admin@arkaria.postgresql.org; Thu, 09 Jan 2025 05:27:25 +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 1tVl4l-00CHrn-SB for pgsql-admin@arkaria.postgresql.org; Thu, 09 Jan 2025 05:27:23 +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 1tVl4l-00CHrc-Gu for pgsql-admin@lists.postgresql.org; Thu, 09 Jan 2025 05:27:23 +0000 Received: from mail-pj1-x102e.google.com ([2607:f8b0:4864:20::102e]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tVl4i-000fm6-0h for pgsql-admin@lists.postgresql.org; Thu, 09 Jan 2025 05:27:22 +0000 Received: by mail-pj1-x102e.google.com with SMTP id 98e67ed59e1d1-2f441791e40so691990a91.3 for ; Wed, 08 Jan 2025 21:27:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1736400438; x=1737005238; darn=lists.postgresql.org; h=to:message-id:subject:date:mime-version:from :content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=PfxJFk8gm6njaL8+//DqYoHDZgsLUX6eXFwFNn8R/Hc=; b=HFJ8llpMBEGOb94XycdOEts/jomUryyPiNp5dl8wzjnDkmVm1pT7FJ+fezC6tJf4Q1 AFXRF2pZRC1tBZ5bxMjnmav87AoXCmfYYYfFr+PuiI4T7CEwB9po3bkmzIcdgvRUg4d5 5o0mjlvrqvnay9gT4lvjAXUeKjpdpSyakMubr8hOWzlDojmeQBGgWGubm7DSo+L1oYc0 Y9Li7E2iEQy35S7cvyYIR9Hv5jahFX+9hrf4/GsbshL3dE5xcJiWCdEX+Zrz4uVE+9Vw TzrEzsdvVcFAg+N754b+6WdELpBUEwuffgPEa3tN+QzVnTJkcFimBrjpyQgCuR6ot2K4 zo+g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1736400438; x=1737005238; h=to:message-id:subject:date:mime-version:from :content-transfer-encoding:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=PfxJFk8gm6njaL8+//DqYoHDZgsLUX6eXFwFNn8R/Hc=; b=MEgMhRJRwrStfOf1m0fdjtAEbhfmjn+DoUZvo0JOhp48SzdNm1icd9tydaZ664G5GC jdcThM8x84PdqdsKg9lc/md0cyyskrnUrzWPYITe+lX4mTBSsiebCxZ7iQRFPu2F/1p5 VdrMlPWdj87vLNYdbXvWxhdGhfbDka7lXPAHFnhpVp+SzhabCprjjsSSiYAQQ5mIaRRG ENPcMo9iCBGSudBbFb/Elyi5C/1LLnJzcPKR5a510OSpH0u6zW5is+koDqHg9yB2PeNb wq7CDbDdNeZG2+oj1x6eUCF4ivt8TZOp3riGu352+L6VoD4AWrCBRza5f4xRc6lvqeAt f+pA== X-Gm-Message-State: AOJu0Yx22ZBxa/Df8Nw/H6GkA1gNj6bYDNETldXiVeCMQ9YHOeBgRg4t l/Y8Js8dNczage7PGKcGElwpEasBQMTezUxs3GLIrwrJXqUce6umhQ0vHg== X-Gm-Gg: ASbGncv2AjTcAlQQHukMXCd1FqgfMf6/UOrM+gxVTRkPhaIjx20Tb6FF5sPssqwlaay IsRG8yeCmBXwceOnqObu3h2c8WG2e7EV/xP9dlcPHEYhmTAHcjfPLY1z9XqxDiYtgdirppV4FIq MPjsV88Q4Ui6dIKvVZ6/bAeRNZTTm/sIrh+HQ5SZo/TMkdqdbsdkTesaSJF39bxGwxzqM9h4S3H 2rrzbU2EdLU5tXUeaIbFhkpDh40KVzZJp5VQI/hy+lDZgs4ytMiyn/Ffsuatqbr9yqXqFGtFN6I Lje4jAsOrd0fx7czai1hlrN5O+FQXHmJYbgSbX8NFFXy X-Google-Smtp-Source: AGHT+IE30PsqEZIYW98OyqQ9C/CZsu3jrNuoqoWDD0e06T3/UpvxqaypNXNUty4k85q3ZSIdSWhpKA== X-Received: by 2002:a17:90b:1f8a:b0:2ee:c9d8:d01a with SMTP id 98e67ed59e1d1-2f548f33b54mr8031597a91.11.1736400438115; Wed, 08 Jan 2025 21:27:18 -0800 (PST) Received: from smtpclient.apple (syn-172-115-078-227.res.spectrum.com. [172.115.78.227]) by smtp.gmail.com with ESMTPSA id 98e67ed59e1d1-2f5593d07cbsm446215a91.3.2025.01.08.21.27.17 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 08 Jan 2025 21:27:17 -0800 (PST) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable From: Teja Jakkidi Mime-Version: 1.0 (1.0) Date: Wed, 8 Jan 2025 21:27:06 -0800 Subject: Credcheck max_auth_failure Message-Id: <5BC62BD6-1C34-4698-99ED-9267F46341A8@gmail.com> To: pgsql-admin X-Mailer: iPhone Mail (21G93) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hello Admins, We are trying to setup password policies on open source Postgres 14 (on SUSE= Linux) using credcheck on an instance that has got stand by setup on other s= erver. On primary, Installed the binaries, created the extension and enabled below p= arameter: credcheck.max_auth_failure to 3; 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 work= ing. Restarting instance will get the banned user working but restarting who= le instance to activate one user is not a feasible solution. 2. The same parameter is not working on the stand by instance. Even after 3 f= ailed attempts user is still active. Please let me know if you are aware of any solutions. Thanks, J. Teja.=