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 1qJf06-0008Pg-DC for pgsql-general@arkaria.postgresql.org; Wed, 12 Jul 2023 18:55:46 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1qJez5-0001Yv-LB for pgsql-general@arkaria.postgresql.org; Wed, 12 Jul 2023 18:54:43 +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 1qJez5-0001Yg-0B for pgsql-general@lists.postgresql.org; Wed, 12 Jul 2023 18:54:43 +0000 Received: from tamriel.snowman.net ([2001:470:e38f::11]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qJez1-0004LV-EG for pgsql-general@lists.postgresql.org; Wed, 12 Jul 2023 18:54:42 +0000 Received: by tamriel.snowman.net (Postfix, from userid 1000) id BF5BB5F7B7; Wed, 12 Jul 2023 14:54:32 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=snowman.net; s=dkim; t=1689188072; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=m7w7ikP2nA1bVgjOnRzG8p9LDoDptPqru1gISfW2Sw8=; b=n+ArHHHR+kOjpmoORUTBH3s2OZ9aqojbr+TNPb8MQ+XZ1LofnRoyKBFtcAHybllVxDqXSC KPQll/jdAAkO0ltINZzN0LpqRCetnn5ll4g68Ww0tJKEwyMDWOxItSPUePjh1gyrI+GqUQ 4iEFkX2l3CvRD2A3oa/ZoLLGB3DschM= Date: Wed, 12 Jul 2023 14:54:32 -0400 From: Stephen Frost To: Lingesan Jeyapandy Cc: "pgsql-general@lists.postgresql.org" Subject: Re: Requesting Information for GSSAPI Message-ID: References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="wg1+bl5+4gu4edbj" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/2.1.4 (2021-12-11) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --wg1+bl5+4gu4edbj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Greetings, * Lingesan Jeyapandy (Lingesan.Jeyapandy@gilead.com) wrote: > We have configured postgres GSSAPI setup on Linux server. We have huge = domain AD users in our org. >=20 > But we are looking to limit access only to setup AD distributed groups. I= s there any way to control access only at AD distribution list user can onl= y access gssapi configured postgres environment. >=20 > Our postgres version is 15. To be able to log into the PG server, an account in PG has to exist. If it doesn't, then the user won't be able to log in. There are some options for sync'ing specific AD groups into PG accounts, eg: https://github.com/larskanis/pg-ldap-sync Thanks, Stephen --wg1+bl5+4gu4edbj Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEwf6gbxKhD863zrx/7WyKOINHZFUFAmSu9uYACgkQ7WyKOINH ZFXfew//Uw8sTgmZI8jgpbbmUmzRAB46nX9b9vGrulW6j4SL7K9S7yAbtD9PDVKA C1irvU6BatWaFvEEQjeL84yRqlOmwlqFwkrIRiT0uhGL+cqIv2BGpy1GaCvy1tHw 0BBr8rQSmYWUMQbADdusc7c7259heyyew+QdHgNVTc4CQh+FZUhFDDkFz8yTOWhw yDF0nDvu/9elrVyLQu99klj/NuA30hY/ZrF2Z3qZE8dLQRTGCPqe2sk+YDQq8ovr jM9OIbSEKsif0w4iLYuVDIwzS+24AxPyIMgconRheODEktU1MFkz3PS2ek1Mb4ED l1aazrWk+bTkgd/QalW1t8Um35obqEuUn3v6zYQDORMluYlwIApia/bIJgv7TCx6 qEwncCoRSh7VD5BDhjaUk+Z7+Bqs8+Oj5E7l0fh+dIXbmd/AN3VYr/29373YQ1TL WEqBz0cjxUlVGvYrZQWVvXQT75+Avrtun+nJhedNq7Wz0fPwkCHgl9RHdo7t9EIg aWSjyygPcfPIiTNRyvIzWVbU6Tm9GK5WQMH9EkWWwjhl3pI1eA3/rTBTU/excJU/ EpC3w37aYeU4JBx04zv1qLwT10MNMSHhei+HjGxOymo6pWUMBC3IeHDLX3MztRLv 9az6tExE+kTqGcseVNu0emzJuv69fUWeIfkGYtdmbJqdYYEd7Y8= =z1mQ -----END PGP SIGNATURE----- --wg1+bl5+4gu4edbj--