Rename useWebAuthn to useMfa and handle SSO challenges #47819
Merged
Conversation
This file contains 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
avatus
added
the
no-changelog
avatus
changed the title
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
Joerger
approved these changes
Oct 22, 2024
ryanclark
approved these changes
Oct 23, 2024
public-teleport-github-review-bot
bot
removed request for
kimlisa and
kiosion
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 PR is mostly a rename/refactor. SSO challenges will still not be received until SSO as MFA is merged.
The reason for this change is to have a single hook that can handle/response to all challenge types instead of just webauthn. So now we can have all of our MFA logic in
useMfainstead.Will follow the backports needed for the entire feature when that time comes.