Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fxByB-0006Xh-2h for pgsql-admin@arkaria.postgresql.org; Tue, 04 Sep 2018 14:06:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fxBy9-0000fX-DQ for pgsql-admin@arkaria.postgresql.org; Tue, 04 Sep 2018 14:06:13 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fxBy9-0000fO-2S for pgsql-admin@lists.postgresql.org; Tue, 04 Sep 2018 14:06:13 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fxBy1-0005fx-Ul for pgsql-admin@postgresql.org; Tue, 04 Sep 2018 14:06:11 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id w84E64U3030656; Tue, 4 Sep 2018 10:06:04 -0400 From: Tom Lane To: Praneel Devisetty cc: pgsql-admin@postgresql.org Subject: Re: User to get locked after three wrong login attempts. In-reply-to: References: Comments: In-reply-to Praneel Devisetty message dated "Tue, 04 Sep 2018 13:18:52 +0530" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <30654.1536069964.1@sss.pgh.pa.us> Date: Tue, 04 Sep 2018 10:06:04 -0400 Message-ID: <30655.1536069964@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Praneel Devisetty writes: > We have a requirement , where we require a user to get locked after three > wrong login attempts. The usual recommendation is to configure Postgres to use PAM authentication; then you can set up any weird requirements like this one in the PAM configuration. regards, tom lane