public inbox for [email protected]  
help / color / mirror / Atom feed
From: Dave Page <[email protected]>
To: Aditya Toshniwal <[email protected]>
Cc: pgadmin-hackers <[email protected]>
Subject: Re: Role based access control discussion
Date: Mon, 17 Mar 2025 10:17:47 +0000
Message-ID: <CA+OCxowS_RUiwOvNgDcyaxe1OqLrL5DfkLhcWnzJKRHn8bF5FQ@mail.gmail.com> (raw)
In-Reply-To: <CAM9w-_=kr_+D0C1TugyoebESyA6FXjLjw9ekHUwS4Hk2F9H8Jw@mail.gmail.com>
References: <CAM9w-_n9sUD1i_qzfowp5=CS0voUnmcGX-UeK8pZ5k3+xuHtLQ@mail.gmail.com>
	<CA+OCxowN3uKQLWTf6F1j7_Zo_72CVj+jue4XjOdnRp3LHxH7Qw@mail.gmail.com>
	<CAM9w-_kjvSGfZ+K1qFABhYfE0kCJ0gDWU3ZyT-Ywb0AEX8=3eg@mail.gmail.com>
	<CA+OCxowMMr_9xB0Dn6H0zRZza3kjztFhijvd1YWLzUZ7Rf4C9g@mail.gmail.com>
	<CAM9w-_=0JzmiyxGK0cc31MwvJxTPiDCqhiAo0Jwaqzo-E3=W4g@mail.gmail.com>
	<CA+OCxoxKwn2Lr=SpuxyhANsip4DgML15mZu0cMsvjebt-Y6m7Q@mail.gmail.com>
	<CAM9w-_mYe2YkHG4kPg64qvPnwS9rLxYC4dC4TL4WNdPk0V1Ogw@mail.gmail.com>
	<CA+OCxoy-rEJmyhiTf9zNn=+aMBEcLZZGuqLm990VbQm-ixYAUQ@mail.gmail.com>
	<CAM9w-_=BE54EPYQ3AV==QdpGwmTg9duto8JMDxchEQm+wy6W_g@mail.gmail.com>
	<CAM9w-_mC92v+pgpy_HH7kUDB9-ugiipAFGoDRViPYroiYCTnUA@mail.gmail.com>
	<CA+OCxowJNrm2-JzPcPVEBUmRRUx_OhogCNP5XSzSphxPdkqFKw@mail.gmail.com>
	<CAM9w-_mNhvraRkQBZh+QXfUd-rasWBwEW55QynhU2cGogGzTQg@mail.gmail.com>
	<CA+OCxoyPd2JaRmpLmhuJC50gdGQ8ix38NHa=4J7tJ2BhXdok+A@mail.gmail.com>
	<CAM9w-_=kr_+D0C1TugyoebESyA6FXjLjw9ekHUwS4Hk2F9H8Jw@mail.gmail.com>

On Mon, 17 Mar 2025 at 10:11, Aditya Toshniwal <
[email protected]> wrote:

>
>
> On Mon, Mar 17, 2025 at 3:39 PM Dave Page <[email protected]> wrote:
>
>> Hi
>>
>> On Mon, 17 Mar 2025 at 09:39, Aditya Toshniwal <
>> [email protected]> wrote:
>>
>>> Hi Dave,
>>>
>>> On Mon, Mar 17, 2025 at 3:00 PM Dave Page <[email protected]> wrote:
>>>
>>>> Hi
>>>>
>>>> On Mon, 17 Mar 2025 at 09:11, Aditya Toshniwal <
>>>> [email protected]> wrote:
>>>>
>>>>> Hi Dave,
>>>>>
>>>>> Essentially, the permissions can be based on the menus:
>>>>>
>>>>> Object Explorer
>>>>>
>>>>>    1. Manage Server Create/Edit/Remove.
>>>>>    2. Create database object (user could still be able to create
>>>>>    using query tool)
>>>>>
>>>>> Definitely not the second one. We shouldn't do anything that is
>>>> enforced in the database server - it's unlikely the two permissions systems
>>>> will remain in sync for more than a few minutes, and we shouldn't be
>>>> duplicating server functionality anyway.
>>>>
>>> Yeah. So should I proceed with the implementation?
>>>
>>
>>
>> If that’s what Akshay wants you working on, then sure :-)
>>
>
> I was waiting for confirmation if the pgAdmin team would accept it or not
> :)
>

My concerns have been answered, so it's good with me.

-- 
Dave Page
pgAdmin: https://www.pgadmin.org
PostgreSQL: https://www.postgresql.org
pgEdge: https://www.pgedge.com


reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: Role based access control discussion
  In-Reply-To: <CA+OCxowS_RUiwOvNgDcyaxe1OqLrL5DfkLhcWnzJKRHn8bF5FQ@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox