This repository was archived by the owner on Jul 17, 2024. It is now read-only.
oAuth: store token in a file accessible by EOS #7
Conversation
This file contains hidden or 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
diocas
force-pushed
the
oauth_integration
branch
from
3c2431a to
8458ce6
Compare
|
Keeping the KRBCC code for now, as it might be needed. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
We will start using oauth tokens to authenticate to EOS. It's still not enabled in all the EOS instances, but we can start playing with one of them.
Since we need access to the user directory right in the startup script, I've added the logic to create the file that FUSEX uses to read the access token. We will have an extension that will do the update, but this will come as a server extension (swan-cern/jupyter-extensions/issues/27).
Since we will no longer have a kerberos token, we also need to remove the code that creates a separate
KRB5CCNAME.@prasanthkothuri I've removed the code in this PR, but I guess it's preferable to keep it for now for the k8s deployment?