Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add more path authorization enforced tests #40

Merged
merged 6 commits into from
Nov 2, 2022
Merged

Conversation

federicaagostini
Copy link
Contributor

@federicaagostini federicaagostini commented Sep 21, 2022

This PR was requested during a DOMA BDT meeting, following the discussion in issue WLCG-AuthZ-WG/common-jwt-profile#21.

Here more path authorization enforced tests are added, in particular

  1. storage.read:/foobar allows to read into the /foobar directory
  2. storage.read:/foo does not allow to read into the /foobar directory
  3. Create directory allowed with storage.create scope
  4. Create directory not allowed with storage.create scope and partial path
  5. storage.read scope with path not compliant with RFC3986 is rejected.
    In this case we check that a GET HTTP request returns a forbidden status on the existing resource /wlcg-jwt-compliance/<uuid>/foobar with a bearer token that has a storage.read:/foobar scope
  6. Trailing slash allows to read into a directory.
    This test is excluded from the CI (i.e. is not present in the summary email report) since I guess is still under discussion. What we're testing is that a storage.read:/foobar/ scope allows to read into an existing /foobar directory, while storage.read:/foo/ and storage.read:/foobar forbids to read into that directory (obviously this test will never success if test 1 above passes as well).

The tests number 2 and 4 are the ones that breaks the fully compliance of XRootD and StoRM WebDAV sites, thus they have been tagged as not-critical (while the remaining ones are critical). In this way one can filter the test report by tag to check directly the result.

The summary tests report of this PR is available here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant