questdb icon indicating copy to clipboard operation
questdb copied to clipboard

Ability to add users and control permissions per table.

Open newskooler opened this issue 4 years ago • 2 comments

Is your feature request related to a problem? Please describe. If you have an organization, where you want different people (or teams) to be able to view different tables. In addition you want want to allow those who view a table, ability to edit (add / remove) and drop table altogether. It's unclear to be how this may be achieved currently with QDB.

Describe the solution you'd like It would be cool if users can be created - thus allowing access to the DB and for each user to be able to control their view / edit / delete permissions. If this can be done through the UI for an admin user - even better.

Describe alternatives you've considered @ideoma suggested changing FS permissions on directory, so this could be definitely one approach I guess. Alternatively I was thinking that exposing the data via REST (or another layer) and handling permissions there is another way of acheving similar results. Downside being that other users don't know / interact directly with the backend.

Additional context None.

newskooler avatar May 10 '21 12:05 newskooler

I think this feature request is a duplicate of: https://github.com/questdb/questdb/issues/170 ?

newskooler avatar May 26 '21 14:05 newskooler

Clarification note on the desired use-case:

If we only want to create an authorization structure regarding table reads - that's achievable via an API layer on top.

If we'd like to have some permission structure for the people who have direct access to QuestDB (backend dev or whoever) then that's only possible with separate QuestDB instances. Ideally that would be possible via QuestDB natively such that you can have multiple devs working on tables with various view / edit permissions. This will also create a safer dev environment where not everyone can drop / alter tables, etc.

newskooler avatar Oct 05 '22 08:10 newskooler