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 1tVl9c-00BD6s-I4 for pgsql-admin@arkaria.postgresql.org; Thu, 09 Jan 2025 05:32:24 +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 1tVl9c-00CSX2-13 for pgsql-admin@arkaria.postgresql.org; Thu, 09 Jan 2025 05:32:23 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tVl9b-00CSWs-M8 for pgsql-admin@lists.postgresql.org; Thu, 09 Jan 2025 05:32:23 +0000 Received: from mail-oi1-x22c.google.com ([2607:f8b0:4864:20::22c]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tVl9Z-000eNx-0e for pgsql-admin@lists.postgresql.org; Thu, 09 Jan 2025 05:32:22 +0000 Received: by mail-oi1-x22c.google.com with SMTP id 5614622812f47-3eb790888c6so145459b6e.2 for ; Wed, 08 Jan 2025 21:32:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1736400741; x=1737005541; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=acrHbPIIrRv+8SDpSMoH697xZ2I5zzz6dHmHLUL5MWY=; b=Hff48ukK3DZw5QZTHFiHf3nwtXJTVus4DeOEX+XIDWTiCnsk7q65Qn4DGnUjwEnjXy A/79W0Xv229XYfrudXdOj9+4uHeGKY83ogxF5kAUL2IUraBbmKxW+xpZCxGGaSarZXFj AGmj3BKdUz4X8expKNAvxp+W+pTXbkxiUE/D5JNWSJdtaiGyH0exNc/WgSu5UaGZ803A 0Wl3ayt2jY0VJhtomYBqMUs4ezIt8O2MoJa9HiYFd43rlfkE5z8IllNGtE6f5B2Z/AYb MGYiL7zjsNoMkMi+X/Rfipfm7Od8a71Y3LZ+x9Z4hwzKVrhmzq901VvJu58hH7xwKHdx rPQQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1736400741; x=1737005541; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=acrHbPIIrRv+8SDpSMoH697xZ2I5zzz6dHmHLUL5MWY=; b=Dym0XWP9OHMYkOmZy5KG24/Iqg3T0AgxAoRUTzrShCZEmaGRKH8oVtiWcg5bIc4UO+ RPrtRi0+47DNNSdGdh1JUllodx5ZtNqU5bqVXbdqbmR05gofDTzP1FhUUlNa3azlK2KN e/kvZiM1CrIHIf/IUen5dSWv3/xB4d82fVUfZ63LvAxuih1S+mk7mqwN44nVKVbwv9vE jmLb2uJ1M5obcR0TkofC9fgDn3GZMyuwlp1f8ZCWTVELfUm7CYA1p84iD7ogPRErtCFX HwMqsz+yHdudFTwMBrCyGgRWRqdlmZpZaC0QBQGQbeCkZ6wjaUPX6vcrFz3SUgAFZPXy 69Ug== X-Gm-Message-State: AOJu0YxgjH897ROtgk5p6NX3DeA7JV4K7tREGC6pJhcInV5HB4Fs0Kqm 1l4UeqHcJHrC2FOQT8Koxzul5tp0FXIZZPtbWpY6BUz52OjAwJLCVNt8KGCXXtGVyrXQM5nBjby 2iT1mSDGPCrmcYsGOFpuU2h+8JlA= X-Gm-Gg: ASbGnct/8prVaTLfK7/wmwGWT27BROvmCjyZRvX+znT3OoMG3ukcs0nt0Fkexi54gpO hv0XTkSnq6E7+f2RtL9gCJsKzLg2+73fgUt58/w== X-Google-Smtp-Source: AGHT+IHKPUg8bFty+bzVk4xQ55K9WbtNhDgfFk0x4xO8Bv8tG9X2GfLLlIOjvnACd70mk8g029LqRMEloIY/FWVXdok= X-Received: by 2002:a05:6808:218c:b0:3e5:fd5a:c39b with SMTP id 5614622812f47-3ef2ebc51ccmr3625368b6e.4.1736400740945; Wed, 08 Jan 2025 21:32:20 -0800 (PST) MIME-Version: 1.0 Received: by 2002:a05:6802:1a87:b0:577:9519:f64a with HTTP; Wed, 8 Jan 2025 21:32:20 -0800 (PST) In-Reply-To: <5BC62BD6-1C34-4698-99ED-9267F46341A8@gmail.com> References: <5BC62BD6-1C34-4698-99ED-9267F46341A8@gmail.com> From: "David G. Johnston" Date: Wed, 8 Jan 2025 22:32:20 -0700 X-Gm-Features: AbW1kvbGO6w5Hxc5hx9OISYcPr0Ge99eFJdYr-ewmK4ehHZVRyqTHeXPf-9n45k Message-ID: Subject: Re: Credcheck max_auth_failure To: Teja Jakkidi Cc: pgsql-admin Content-Type: multipart/alternative; boundary="0000000000005a1890062b3f4d84" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000005a1890062b3f4d84 Content-Type: text/plain; charset="UTF-8" On Wednesday, January 8, 2025, Teja Jakkidi 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. --0000000000005a1890062b3f4d84 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wednesday, January 8, 2025, Teja Jakkidi <teja.jakkidi05@gmail.com> wrote:

1. The parameter is working as expected on primary and banning the id in th= e 3rd attempt with wrong password.
However, I am not able to figure out how to get the banned user back to wor= king. Restarting instance will get the banned user working but restarting w= hole instance to activate one user is not a feasible solution.


You should read its docs.=C2=A0 It discuss= es this.


David J.

--0000000000005a1890062b3f4d84--