Added globus session update --scope #1
Closed
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.
What?
--scopetoglobus session updatewhich defines additional scopes to request when running the user through a login flow.globus flows start <flow_id>to always include the flow scope in remediating resolutionglobus session updatecommand.Why?
In the current cli,
globus flows start <flow_id>recommends usingglobus session updatewith exclusively the attached policy id from the api-returned GARE. This command doesn't function as expected however because of how flows operate as individual resource servers.Inserting the scope can allow remediation login commands recommendations to ensure that any a user login will return scoped tokens not just for statically known resource servers, but also any dynamically discovered ones.
Testing