Deprecate pendingSSO, missingMFA fields #1651
Open
+9
−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
coyotte508
approved these changes
Jul 24, 2025
There was a problem hiding this comment.
note that there is auth0 and nextauth to update probably 😬
(I think we don't care that much about auth0, given the painful submission process, but nextauth is here: nextauthjs/next-auth#12884)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 pull request updates the
UserInfointerface inpackages/hub/src/lib/oauth-handle-redirect.tsto improve how security restrictions are represented. It introduces a newsecurityRestrictionsfield and marks two existing fields as deprecated.Updates to the
UserInfointerface:securityRestrictionsfield to represent various security restrictions ("mfa","sso","ip","token-policy") in a unified way.pendingSSOfield, recommending the use ofsecurityRestrictionswith"sso"instead.missingMFAfield, recommending the use ofsecurityRestrictionswith"mfa"instead.