Repository navigation
feat(config): add phishing_resistant_only system config key - #89
Merged
Merged
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.
Refs fells-code/seamless-auth-api#177.
Adds
phishing_resistant_only(boolean, defaultfalse) toSystemConfigSchemaandSystemConfigPatchSchema. The API enforces it in a follow-up PR. When it is on, the only way to start a session is a passkey. Email and phone codes, magic links, TOTP and OAuth are refused, whateverlogin_methodssays, with one exception: a code is accepted once to verify a new account's address before its first passkey is enrolled.Defaults to off, so existing deployments parse and behave as before. Minor bump.
Verified with lint, typecheck, format check, tests (278 passed) and build.