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 1p3MGd-0001dB-Kz for pgsql-admin@arkaria.postgresql.org; Thu, 08 Dec 2022 19:09:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1p3MGc-00078Y-49 for pgsql-admin@arkaria.postgresql.org; Thu, 08 Dec 2022 19:09:10 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1p3MGb-00077z-AP for pgsql-admin@lists.postgresql.org; Thu, 08 Dec 2022 19:09:09 +0000 Received: from mailrelay2-3.pub.mailoutpod2-cph3.one.com ([2a02:2350:5:501::1]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1p3MGW-0000AR-H0 for pgsql-admin@postgresql.org; Thu, 08 Dec 2022 19:09:07 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=venaas.org; s=rsa2; h=content-type:mime-version:message-id:date:subject:in-reply-to:references:cc: to:from:from; bh=vc2fcWbdXJaIaieDxPyNDmZW0BxgBf/6QdWm22bRxDM=; b=NDqWoDSE5LGu7max6WAf5JJwi/Tqb0ac7TWQCSD4YajHqCKxF4OxoHIc8G7eoZlepI5dtw9FCMqLR ZU0GccwoBTW/hTLm3231zZ8VHxylWvA4SBCJ0UYR7q3pRh/X1yOwqwT0caNOqqmGH493bxDxBNNzXO KtjywSIE91G1Ef0JfISKqfcRWtezO0YaYh0BsuUMfCx85ydoYTJWNVBnDAVH5nJq0RYcNGMHFLoNPK kRUZcMhaDwcklJtyNQoIxc3Ol8mjK8f17xfj/PBT3dsDA2bB04Djshr6N9mFQO6dI3qSgwl+aKboxY eYonSSaPG1HhiUI3L03q5NXZBpAckzg== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=venaas.org; s=ed2; h=content-type:mime-version:message-id:date:subject:in-reply-to:references:cc: to:from:from; bh=vc2fcWbdXJaIaieDxPyNDmZW0BxgBf/6QdWm22bRxDM=; b=aHm6KGgO0drUE512u97wL5UOJvVUwwt/HchsQNpo/YJrS8J2u58xUBFchAV9V4mdyqfc2eVjVkzMY fgJb2ZqDA== X-HalOne-ID: c45f32bf-772b-11ed-86c8-93f0a866dfbb Received: from onecom-eas-backend-production-5845c86c75-kpbbd (service.pub.live1-k8s-cph3.one.com [46.30.212.67]) by mailrelay2 (Halon) with ESMTPSA id c45f32bf-772b-11ed-86c8-93f0a866dfbb; Thu, 08 Dec 2022 19:08:59 +0000 (UTC) From: "Gunnar Venaas" To: "'JP Pozzi'" ,"'M Sarwar'" CC: "'pgsql-admin'" References: <1248013365.2011.1670455113858.JavaMail.zimbra@jppozzi.dyndns.org> In-Reply-To: <1248013365.2011.1670455113858.JavaMail.zimbra@jppozzi.dyndns.org> Subject: RE: Using non-Super user with PgAmdin Date: Thu, 8 Dec 2022 20:08:57 +0100 Message-ID: <00b501d90b38$85dd5790$919806b0$@venaas.org> MIME-Version: 1.0 Content-Type: multipart/alternative;boundary="----=_NextPart_000_00B6_01D90B40.E7A39450" X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQKyrSoHm0Xdpp1FyhW3DfyyZaFVmgEhrV53AhxRRGkB7OM4DgFh0HCerHywhQA= Content-Language: no List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multipart message in MIME format. ------=_NextPart_000_00B6_01D90B40.E7A39450 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable This is not a =E2=80=9Csmart=E2=80=9D approach. =20 The application should run with =E2=80=9Cleast privilege=E2=80=9D, and = the developers should develop within the same context. =20 There are far to many applications that demands some sort of elevated = permissions to work. =20 =20 =20 =20 Gunnar Venaas gunnar@venaas.org =20 932 85 069 =20 From: JP Pozzi =20 Sent: torsdag 8. desember 2022 00:19 To: M Sarwar Cc: pgsql-admin Subject: Re: Using non-Super user with PgAmdin =20 Hello, =20 It's quite normal and smart not to give developers superuser rights and = Pgadmin is OK with that. Regards JP P =20 _____ =20 De: "M Sarwar" > =C3=80: "pgsql-admin" > Envoy=C3=A9: Jeudi 8 D=C3=A9cembre 2022 00:00:09 Objet: Using non-Super user with PgAmdin =20 Hello All, After working in the databases for the decades, recently I started a = project postgress side newly. I have a question on pgadmin access. Can I use other than super user to login into pgadmin? I am trying to provide access to all the development team members = without giving them access to super user, postgress. Thanks, Sarwar 8 times ocp dba 3 cloud certificates =20 =20 ------=_NextPart_000_00B6_01D90B40.E7A39450 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

This is not a = =E2=80=9Csmart=E2=80=9D approach.

 

The = application should run with =E2=80=9Cleast privilege=E2=80=9D, and the = developers should develop within the same context.

 

There are = far to many applications that demands some sort of elevated permissions = to work.

 

 

 

 

Gunnar Venaas

gunnar@venaas.org

932 85 069

 

From: JP Pozzi = <jpp@jppozzi.dyndns.org>
Sent: torsdag 8. desember 2022 = 00:19
To: M Sarwar = <sarwarmd02@outlook.com>
Cc: pgsql-admin = <pgsql-admin@postgresql.org>
Subject: Re: Using = non-Super user with PgAmdin

 

Hel= lo,

 

It'= s quite normal and smart not to give developers superuser rights and = Pgadmin is OK with that.


Reg= ards


JP = P

 

De:= &qu= ot;M Sarwar" <sarwarmd02@outlook.com>
= =C3=80: "pgsql-admin" <pgsql-admin@postgresql.org= >
Envoy=C3=A9: Jeudi 8 D=C3=A9cembre 2022 = 00:00:09
Objet: Using non-Super user with = PgAmdin

 

Hello = All,

After working in = the databases for the decades, recently I started a project postgress = side newly.

I have a = question on pgadmin access.

Can I use other = than super user to login into pgadmin?

I am trying to = provide access to all the development team members without giving them = access to super user, postgress.

Thanks,

Sarwar

8 times ocp = dba

3 cloud = certificates

 

=

 

------=_NextPart_000_00B6_01D90B40.E7A39450--