apache / apache/polaris

Back/forwards compatible privileges

Open
#554 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Java
Stars
2.1k
Forks
522
Avg merge
1d 22h
Merged PRs (30d)
137

Description

### Describe the bug

`polaris-management-service.yml` defines all privileges as enum (values). This approach gets in the way when new privileges are added (client & server are built from different versions of `polaris-management-service.yml`).

The enum-approach is also not going to work with the short/mid-term goal to have "pluggable authZ" in Polaris, where authZ implementations can define their own privileges.

Contributor guide

Open the contributing guide

Research direction

Read polaris-management-service.yml first to understand how privileges are currently represented and how client/server version differences arise. Done means defining a compatibility approach that permits newly added and pluggable privileges without enum-version breakage; the issue names no tests or entry points.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api, authorization
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.