Investigate how descendent roles are handled regarding read
#691
Labels
good first issue
Good for newcomers
hacktoberfest
For the hacking month of October
testing
related to new or existing tests
Goal: confirm with @csuwildcat on expected behavior, investigate if actual behavior matches outcome, write tests if they don't already exist.
Maybe everything works, but it is unclear to me how the descendent (context) role declared in
thread-role.json
is being used for protocol authorization:It would be good to investigate if this is a special case only because we so happen to have the
contextId
of the thread? What happens if the descendent role specified is deeper, e.g.thread/foo/bar/baz
, just to make sure there is no security holes.Additional info I added at the time of this issue creation, but no longer remember/understand why but afraid to remove:
If we were to disallow descendent roles, we'd do:
The text was updated successfully, but these errors were encountered: