docs(openapi): clarify AAL2 requirement for password/email updates when MFA is enabled#2314
Open
toklas495 wants to merge 1 commit intosupabase:masterfrom
Open
docs(openapi): clarify AAL2 requirement for password/email updates when MFA is enabled#2314toklas495 wants to merge 1 commit intosupabase:masterfrom
toklas495 wants to merge 1 commit intosupabase:masterfrom
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
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.
This PR documents existing Supabase Auth behavior where updating
email or password requires an AAL2 session when MFA (TOTP or SMS)
is enabled.
Sessions obtained from password recovery links are AAL1 by default
and will be rejected by PUT /user when attempting to update
email or password.
This change does NOT modify runtime behavior.
It clarifies the contract in the OpenAPI spec to avoid confusion.
Related issue: