Skip to content
This repository was archived by the owner on Jan 7, 2026. It is now read-only.

BEP-1008 (new): Apply RBAC#9

Merged
achimnol merged 1 commit into
mainfrom
topic/rbac
Jun 27, 2025
Merged

BEP-1008 (new): Apply RBAC#9
achimnol merged 1 commit into
mainfrom
topic/rbac

Conversation

@HyeockJinKim
Copy link
Copy Markdown
Collaborator

No description provided.

@HyeockJinKim HyeockJinKim requested a review from fregataa June 26, 2025 08:08
@HyeockJinKim HyeockJinKim self-assigned this Jun 26, 2025
@HyeockJinKim HyeockJinKim changed the title BEP1008: Add RBAC BEP BEP1008: Apply RBAC Jun 26, 2025
Copy link
Copy Markdown
Member

@fregataa fregataa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. How about using a scope name "global" rather than "system"?
  2. What happen if a client requests list of Entity in a "domain" scope but the client has a read permission only in a "project" scope which belongs to the domain? Would the client rejected or get the entity in project scope?
    To clarify how RBAC handles such cases, let's add more details about checking permissions in nested scope recursively in RBAC check flow section.
  3. Does "Role" belong to any scope? Or every Role can be globally used? Should the name of Role is unique globally or in a certain scope?
  4. Can the role_permissions.operation column have only "creat", "read" value or can have joined string value like "create,read"?

@achimnol achimnol merged commit a643031 into main Jun 27, 2025
1 check passed
@achimnol achimnol changed the title BEP1008: Apply RBAC BEP-1008 (new): Apply RBAC Jun 30, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants