Expose organization authentication requirements in OAuth flows - #222
Merged
Merged
Conversation
This was referenced Sep 9, 2026
ericmj
marked this pull request as ready for review
September 10, 2026 02:26
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.
OAuth grants now preserve the missing authentication requirements for each organization, including independent SSO and 2FA reasons. Add the shared organization authorization endpoint and pass structured requirements through CLI authentication callbacks so clients can request the required browser verification.
Malformed requirement entries retain the previous authentication state instead of clearing it. Validated with 165 Common Test cases, both properties with 100 generated cases each, and the formatter.
Related: hexpm/hexpm#1913, hexpm/hex#1237.