Add authentication and authorization mechanism #171
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kobs now has a proper mechanism for authentication and authorization. While the authentication of a user should still be handled via an external application like OAuth2-Proxy, the User CR and Team CR and now be used to authorize the authenticated user to access several plugins and resources. For this a User CR must be defined with the ID which is set by the OAuth2-Proxy via the user details header. The user will then get all the permissions from the teams he is a member of. For that the Team CR now contains a new "permissions" property, where the plugins and resources which can be accessed by the teams members are specified.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
kobs now has a proper mechanism for authentication and authorization.
While the authentication of a user should still be handled via an
external application like OAuth2-Proxy, the User CR and Team CR and now
be used to authorize the authenticated user to access several plugins
and resources.
For this a User CR must be defined with the ID which is set by the
OAuth2-Proxy via the user details header. The user will then get all the
permissions from the teams he is a member of. For that the Team CR now
contains a new "permissions" property, where the plugins and resources
which can be accessed by the teams members are specified.