Role-based access control

Open
#6 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
api, authorization, security

Research direction

The issue mentions no files, tests, or entry points. Start by reviewing the QuestDB-side SPI and existing authorization boundaries, then clarify the required scope for table, column, and partition access. Done should be defined by an agreed generic role-based authorization design and explicit integration requirements.

Written by the indexing model from the issue text.

Description

enterprise security

Summary

Generic role-based authorization.

Expected outcome

This feature should make possible attaching third-party APIs via generic SPI on QuestDB side. Users will be able to control access at table, column and possibly partition granularity.

Dominant language
No language data
Stars
7
Forks
0
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from questdb/roadmap

All issues in questdb/roadmap

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.