Document that GlobusApp always requests openid
#1362
Merged
+7
−0
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
This is noted in property documentation for ``scope_requirements``. This is one of a few ways in which users may observe the presence of this scope, but the choices are either to document this on the property or on the top-level class doc. The property is guessed to be more likely to be seen by a user exploring to try to understand their scope requirements. For reference and motivation, see globus#1359
sirosen
requested review from
MaxTueckeGlobus,
aaschaer,
ada-globus,
derek-globus,
kurtmckee and
m1yag1
as code owners
derek-globus
approved these changes
Jan 7, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 is noted in property documentation for
scope_requirements. Thisis one of a few ways in which users may observe the presence of this
scope, but the choices are either to document this on the property or on
the top-level class doc. The property is guessed to be more likely to be
seen by a user exploring to try to understand their scope requirements.
For reference and motivation, see #1359