Origin requires multiple scitokens #1989
Draft
Conversation
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
added 4 commits
February 4, 2025 18:24
-- Not only origins with direct reads capabilites have an entry with u * <namespace> lr -- Adjusted the current tests to account for this
-- Added a function to get the publicReads prefixes -- Added a function to generate the FederationIssuer in the origin's scitoken -- Adjusted the issuer structure to include a boolean for if it's a a federation issuer
-- If the issuer is a federation issuer, the scitokens file will now generate the needed authorization for multi-issue checking
-- Added more tests for the origin authfile based on namespace capabilities -- Adjusted current tests for scitokens to get the new expected output with a federation issue for both public and private namespaces
turetske
added
origin
turetske
force-pushed
the
origin-requires-multiple-scitokens
branch
from
e5286fe to
6167abc
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR updates the origin scitokens and authfiles to reflect the cache auth changes.
If an origin's namespace has direct-read capabilities, the authfile still remains the same. However, if it doesn't, but has PublicRead capabilities, then that path is moved into the origin's scitoken file behind a federation Issuer. Private capabilities now also require that federation issuer.
This is still a draft PR because full testing can't be done until all the other cache auth pieces are complete.