Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jXnCq-0007Jp-Ot for pgsql-admin@arkaria.postgresql.org; Sun, 10 May 2020 14:45:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jXnCn-00074v-Ra for pgsql-admin@arkaria.postgresql.org; Sun, 10 May 2020 14:45:25 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jXnCn-00073x-Jd for pgsql-admin@lists.postgresql.org; Sun, 10 May 2020 14:45:25 +0000 Received: from impout004aa.msg.chrl.nc.charter.net ([47.43.20.28] helo=impout004.msg.chrl.nc.charter.net) by magus.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jXnCb-00012w-7h for pgsql-admin@lists.postgresql.org; Sun, 10 May 2020 14:45:25 +0000 Received: from cerberus.crazybean.net ([24.151.69.73]) by cmsmtp with ESMTP id XnCYjaBVZwzF8XnCYjG4px; Sun, 10 May 2020 14:45:10 +0000 Authentication-Results: crazybean.net; none X-Authority-Analysis: v=2.3 cv=SdVDicZu c=1 sm=1 tr=0 a=YXTuGtgWN9YX+aIhe8tYuA==:117 a=YXTuGtgWN9YX+aIhe8tYuA==:17 a=xqWC_Br6kY4A:10 a=IkcTkHD0fZMA:10 a=sTwFKg_x9MkA:10 a=pGLkceISAAAA:8 a=HaXuuAwOIIB5roqIsEkA:9 a=QEXdDO2ut3YA:10 Received: from [IPv6:2001:470:e117:4:456a:14da:ac4d:e9b7] ( [2001:470:e117:4:456a:14da:ac4d:e9b7]) by cerberus.crazybean.net (OpenSMTPD) with ESMTPSA id bd4943ef (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO); Sun, 10 May 2020 10:45:09 -0400 (EDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) Subject: Re: Deactivate/disable User id in Postgres From: Rui DeSousa In-Reply-To: <74156874-be59-bcf9-b8c9-a7bd85b9a53e@gmail.com> Date: Sun, 10 May 2020 10:45:09 -0400 Cc: pgsql-admin@lists.postgresql.org Content-Transfer-Encoding: quoted-printable Message-Id: <68760C38-3CD2-4348-8DCD-48A7B955BD63@crazybean.net> References: <74156874-be59-bcf9-b8c9-a7bd85b9a53e@gmail.com> To: Ron X-Mailer: Apple Mail (2.3608.80.23.2.2) X-CMAE-Envelope: MS4wfJaM1vCh9lO9o+7eBEXDy3Y8g5SZaPvpX8o3aNVwMZJdcEs4hoUHfiAWry068nLYW/7ei+ZEkzxbcltf8veConD8cI62rdRO2CzByMrpOSMBsp+iggNa gsubDNAjwZrK/A+UXpnMMmloSTz4UJWPKnwfyrX6pwxrtPh6fo7sKbS18GyhBu2XLd4l8ye+anFa3F/bmyAbSDtnQeiic8W/t562nucVBR5nj09q6e0MpAt0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk > On May 10, 2020, at 8:24 AM, Ron wrote: >=20 > On 5/4/20 9:45 AM, Rui DeSousa wrote: >>=20 >>=20 >> Using external authentication is an option too. i.e. using LDAP; = disabling the account in LDAP means the user cannot login. >=20 > That would be a disaster in an enterprise that has many systems, and = uses LDAP/AD for account management. >=20 > --=20 > Angular momentum makes the world go =E2=80=98round. Hmm, enterprises do exactly that and once the account is disabled its = disabled everywhere. Single sign-on is very common practice these days. = I would agree if talking about a targeted specific system temporarily.=20=