feat: add ResourceAccessScopeStrategy #806
Draft
+124
−0
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.
Related to this hydra issue.
This scope strategy splits a scope into resources delimited with
:
.Each resource can have dynamic values if it has the suffix
-*
.The last resource can specify a verb delimited with
.
.The hierarchy of the matcher and scope resources needs to be identical.
Examples:
users.*
matchesusers.read
users.write
does not matchusers.read
users:settings
matchesusers:settings
users:settings
does not matchusers:settings.read
users:client-*.read
does matchusers:client-bar.read
users:client-*
does not matchusers:client-bar.read
users:client-*.*
does matchusers:client-foo.write
Open questions:
Should I make the resource/verb delimiter configurable? What about allowing dynamic resources?