Auto-generate token if the issuer is available #1591
Merged
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
For simple origins, there's one "service user" that has access to the private key. Instead of teaching admins how to manually create a token, then use the client, have the client generate the token immediately when needed.
The cache plugin directory is controlled by environment variable. If the environment variable is set in the `pelican` environment, pass its value along to xrootd. Simplifies testing in environments where the plugin is not installed as root.
bbockelm
added
enhancement
jhiemstrawisc
approved these changes
Sep 30, 2024
Closed
1 task
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 tweak will cause the client to search for the issuer's private key in its local configuration and auto-generate a token as needed. (On simple origin deployments, it's not uncommon for the origin to be run by a single individual who has the private key)
This prevents the user (in this specific case) from needing to know how to create tokens to use Pelican: simply drop the private key into
~/.config/pelican/issuer.jwkand go!