Use an object to describe permission instead of strings#293
Open
thiagodelgado111 wants to merge 1 commit intokeycloak:mainfrom
Open
Use an object to describe permission instead of strings#293thiagodelgado111 wants to merge 1 commit intokeycloak:mainfrom
thiagodelgado111 wants to merge 1 commit intokeycloak:mainfrom
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Hey folks, I noticed that we should use something like
resource:scopefor specifying the resources and scopes we want to enforce the user has access to. Although splitting a string based on:might not work depending on the resource name. If you are using your own URN, as an example, it would yield weird auth requests.I think extending the current format to accept resource and scope as an object or an array of string arrays might easily solve that