Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

✨ authz: add warrants to default rule resolver #155

Open
wants to merge 1 commit into
base: kcp-1.31.0
Choose a base branch
from

Conversation

sttts
Copy link
Member

@sttts sttts commented Dec 2, 2024

What type of PR is this?

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?


Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


@mjudeikis
Copy link

/lgtm
/approve

@sttts sttts force-pushed the sttts-warrants-1.31 branch from eca30de to 49075cf Compare December 12, 2024 15:33
@sttts sttts force-pushed the sttts-warrants-1.31 branch from 49075cf to 565a453 Compare January 16, 2025 21:46
@sttts sttts changed the title 1.31: PoC: ✨ authz: add warrants to default rule resolver ✨ authz: add warrants to default rule resolver Jan 16, 2025
// WarrantExtraKey is the key used in a user's "extra" to specify
// JSON-encoded user infos for attached extra permissions for that user
// evaluated by the authorizer.
WarrantExtraKey = "authorization.kcp.io/warrant"

Choose a reason for hiding this comment

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

warrants? Are we doing Singelton or Plurar here, too?

@mjudeikis
Copy link

Just a nit question for now but lets hold merging until we test this in downstream to see if there is any issues :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants