WIP: Addition of keycloak for auth #514
Closed
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.
The proposed changes work with wis2box's existing architecture without altering any of the existing functionality.
Three additions are required before a first version can be merged:
nginx/oauth2-conf.inc
to ensure that theX-Groups
header added by oauth2-proxy is forwarded to wis2box-authapp.py
are required to:add_group
andremove_group
(equivalent to existingadd_token
andremove_token
)authorize
will also authorize requests where the user's group (defined in keycloak and available to wis2box-auth in theX-Groups
header) has permission to access the topic