Fix email_verified_code usage #4252
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
When a Cozy instance has for authentication the combo magic link + 2FA, and its owner wants to login via the cloudery, we try to avoid a flow with two emails (one for finding the instance domain, and the other with the 6-digits code). To do that, we use an email_verified_code, and the stack needs to change its behavior on the login page when this code is present, which was not done correctly before this commit.
taratatach
approved these changes
Dec 6, 2023
This was referenced Feb 20, 2024
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.
When a Cozy instance has for authentication the combo magic link + 2FA, and its owner wants to login via the cloudery, we try to avoid a flow with two emails (one for finding the instance domain, and the other with the 6-digits code). To do that, we use an email_verified_code, and the stack needs to change its behavior on the login page when this code is present, which was not done correctly before this commit.