feat: per-user Globus token submission for SLURM-level attribution#26
Merged
Conversation
When a Globus access token is supplied, submit_streaming_inference() creates a short-lived Executor authenticated as the caller so that SLURM jobs appear under the user's own identity on the HPC cluster. API-key callers continue using the persistent executor (stored creds). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
GlobusComputeClient.submit_streaming_inference()now accepts an optionalglobus_tokenparameterExecutoris created usingAccessTokenAuthorizerso the SLURM job is submitted under the caller's own Globus identity, giving per-user attribution on the HPC clusterstream/proxy/app.pypassescaller.globus_tokenthrough to the Globus client when Mode A (Globus Token Auth) is activeMotivation
The paper described per-user SLURM attribution as a feature of Mode A (Globus Token Auth), but the implementation was using the proxy's own stored credentials for all job submissions. This brings code and paper into alignment.
Notes
globus_token=Nonepreserves prior behavior exactlyTest plan
gce = self._get_executor()path is taken (log shows no "caller-token executor" message)"Using caller-token executor (per-user SLURM attribution, channel=...)"and SLURM job appears under caller's username🤖 Generated with Claude Code