-
Notifications
You must be signed in to change notification settings - Fork 391
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
✨ auth: Implement user scopes #3235
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In general this look ok. I think :)
d9736ba
to
48915f7
Compare
eb92f8f
to
f9438f4
Compare
920425b
to
9f5086b
Compare
Signed-off-by: Dr. Stefan Schimanski <[email protected]> Co-authored-by: Mangirdas Judeikis <[email protected]> Signed-off-by: Mangirdas Judeikis <[email protected]> On-behalf-of: @SAP [email protected]
Signed-off-by: Mangirdas Judeikis <[email protected]> On-behalf-of: @SAP [email protected] Signed-off-by: Dr. Stefan Schimanski <[email protected]>
Signed-off-by: Dr. Stefan Schimanski <[email protected]>
Signed-off-by: Dr. Stefan Schimanski <[email protected]>
Signed-off-by: Dr. Stefan Schimanski <[email protected]>
lgtm (leaving "real" approval for after the PR has been rebased to kcp-dev/kubernetes). |
Signed-off-by: Dr. Stefan Schimanski <[email protected]>
/lgtm |
LGTM label has been added. Git tree hash: d0572537fdd40869d1c9aa27d7ea12843d4e88ff
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mjudeikis The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Summary
Vendors kcp-dev/kubernetes#157 for
authentication.kcp.io/scopes: cluster:<name>,...
user info extra values that scope down a user to those clusters. In a cluster outside of the users' (potentially existing) scopes, the user is considered authenticated, but it loses it other properties like groups and extra data.This PR uses the mechanism to:
WorkspaceType
owner cannot use the workspace owner identity for other purposes than accessing the logical cluster at hand.This is towards warrant support in #3156.
Related issue(s)
Release Notes