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 <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1qki72-00FrpH-4a
	for pgsql-admin@arkaria.postgresql.org; Mon, 25 Sep 2023 09:42:44 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1qki6z-00HEFk-0B
	for pgsql-admin@arkaria.postgresql.org; Mon, 25 Sep 2023 09:42:41 +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 <mu88+dev@posteo.eu>)
	id 1qki6y-00HEFQ-HX
	for pgsql-admin@lists.postgresql.org; Mon, 25 Sep 2023 09:42:40 +0000
Received: from mout01.posteo.de ([185.67.36.65])
	by makus.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <mu88+dev@posteo.eu>)
	id 1qki6u-006Wjs-Vy
	for pgsql-admin@lists.postgresql.org; Mon, 25 Sep 2023 09:42:39 +0000
Received: from submission (posteo.de [185.67.36.169])
	by mout01.posteo.de (Postfix) with ESMTPS id EEA3124002B
	for <pgsql-admin@lists.postgresql.org>;
 Mon, 25 Sep 2023 11:42:32 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.eu; s=2017;
	t=1695634953; bh=Do7x/UBqJ7/SLeC6cZn0OszjjeTTsS5SCH64tCZ6xrg=;
	h=Date:From:To:Message-ID:Subject:MIME-Version:From;
	b=Sbe6ADUBYhqN20LrRTj7R83jL4KSpVY/RPzs8jB6HGL5ljq/Y/QGlPTX0pLzBaHHh
	 ogtNYVhe04GEmr0dby8cpFfBM9pVJiXE+cEKPdbOlrGAVNPmuFSZMOmpBl0J+mdJZk
	 gcabZXDJVQZDtGkrZMMUm9DVr9iBjyGr1GYB4cx9XnZ9em05k5OKeYO45PDMPtdR7C
	 MpkMgoP6rYNtpWSnwnfnDJPtmvRUO6RTcRumQ1LpRXsLUf59kvObEpN3xPtOGJevnD
	 FHFuxC+8X2C0SSI7uNw2WRreYJ6LoEPJgpkKobNHIjOb9S8GulI28GCeflgiqq6tUG
	 FP0R3px/U1L4Q==
Received: from customer (localhost [127.0.0.1])
	by submission (posteo.de) with ESMTPSA id 4RvHwR6q3Nz9s0S
	for <pgsql-admin@lists.postgresql.org>;
 Mon, 25 Sep 2023 11:42:31 +0200 (CEST)
Date: Mon, 25 Sep 2023 09:42:30 +0000 (+00:00)
From: mu88 <mu88+dev@posteo.eu>
To: pgsql-admin@lists.postgresql.org
Message-ID: <28c7d917-d9fe-4d8b-aee1-5764190d9e5e@posteo.eu>
Subject: Seed pgAdmin roles with Active Directory groups when using Docker
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_6_115132596.1695634950523"
X-Correlation-ID: <28c7d917-d9fe-4d8b-aee1-5764190d9e5e@posteo.eu>
List-Id: <pgsql-admin.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-admin@lists.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-admin>
Archived-At: 
 <https://www.postgresql.org/message-id/28c7d917-d9fe-4d8b-aee1-5764190d9e5e%40posteo.eu>
Precedence: bulk

------=_Part_6_115132596.1695634950523
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Hi,

I want to setup a pgAdmin instance for our team using the Docker deployment. As our organization uses Active Directory, I'd like to assign the pgAdmin User role to a specific AD group when starting the pgAdmin Docker container.

Within the docs I already found the option to use pgAdmin with LDAP, so hopefully accessing our AD should work.

What I didn't find: is it possible to assign a pgAdmin role to an AD group or only to AD users? And if yes, can this automatically happen on Docker container start (e. g. by using an environment variable or a config file similar to servers.json)?

Or put in other words: is it possible that it looks like this after container start only by configuration without any manual interaction?

Best regards!

PS: you find this question here as well: https://dba.stackexchange.com/questions/331385/seed-pgadmin-roles-with-active-directory-groups-when-using-docker

------=_Part_6_115132596.1695634950523
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<html>
 <head>
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
 </head>
 <body>
  <div style="font-family: sans-serif;">
   <span dir="ltr" style="margin-top:0; margin-bottom:0;">Hi,</span>
   <br>
   <br><span dir="ltr" style="margin-top:0; margin-bottom:0;">I want to setup a pgAdmin instance for our team using the Docker deployment. As our organization uses Active Directory, I'd like to assign the pgAdmin User role to a specific AD group when starting the pgAdmin Docker container.</span>
   <br>
   <br><span dir="ltr" style="margin-top:0; margin-bottom:0;">Within the docs I already found the option to use pgAdmin with LDAP, so hopefully accessing our AD should work.</span>
   <br>
   <br><span dir="ltr" style="margin-top:0; margin-bottom:0;">What I didn't find: is it possible to assign a pgAdmin role to an AD group or only to AD users? And if yes, can this automatically happen on Docker container start (e. g. by using an environment variable or a config file similar to servers.json)?</span>
   <br>
   <br><span dir="ltr" style="margin-top:0; margin-bottom:0;">Or put in other words: is it possible that it looks like this after container start only by configuration without any manual interaction? </span>
   <br>
   <br><span dir="ltr" style="margin-top:0; margin-bottom:0;">Best regards!</span>
   <br>
   <br><span dir="ltr" style="margin-top:0; margin-bottom:0;">PS: you find this question here as well: https://dba.stackexchange.com/questions/331385/seed-pgadmin-roles-with-active-directory-groups-when-using-docker</span>
   <br>
  </div>
 </body>
</html>
------=_Part_6_115132596.1695634950523--