-
Notifications
You must be signed in to change notification settings - Fork 136
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
gplazma: oidc update explicit AuthZ parsing
Motivation: The WLCG JWT Profile describes how JWTs may include explicit authorisation statements in the 'scope' claim (e.g., `storage.read:/foo`). When processing a token, the oidc gPlazma plugin decides whether the token carries explicit AuthZ statements. If it does, then the resulting login will suspend namespace-based authorisation and fully honour the authorisation from the token. There are a few issues with how dCache currently parses these explicit AuthZ statements. 1. The profile describes how the resource identifier is optional (e.g., `storage.read` is valid), but dCache scope parsing currently rejects explicit AuthZ if the resource identifier is missing. 2. The profile describes several explicit AuthZ statements (e.g., `compute.read`). Currently, dCache completely ignores these statements. However, this is not complete correct because such compute explicit AuthZ statements indicate the token (in general) is carrying explicit AuthZ. Therefore, the presence of compute explicit AuthZ statements and a lack of any storage explicit AuthZ statements should result in dCache rejecting requests by that token. Modification: Update scope parsing components to relax the requirement on having a resource identifier. An explicit AuthZ statement without a resource identifier is equivalent to adding `:/` to the statement (e.g., `storage.read` interpreted as `storage.read:/`). Add extra valid values for the "compute.\*" explicit AuthZ statements. This are ignored by the rest of dCache, but their presence will result in dCache considering the token as one with explicit AuthZ. Result: dCache will now accept non-targeted explicit AuthZ statements in the scope claim (e.g., `storage.read`). dCache will consider tokens containing compute explicit AuthZ statements but without any storage explicit AuthZ statements as tokens with explicit authorisation; the lack of any storage explicit authorisation statements will result in all requests with that token being denied. Target: master Requires-notes: yes Requires-book: no Request: 9.2 Request: 9.1 Request: 9.0 Request: 8.2 Patch: https://rb.dcache.org/r/13996/ Acked-by: Dmitry Litvintsev
- Loading branch information
1 parent
49661e6
commit 094c171
Showing
3 changed files
with
182 additions
and
14 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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