Open
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
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.
Adds a first-class OTP (one-time password) authentication strategy to AshAuthentication. Users receive a short code (e.g.
"XKPTMH") via email/SMS instead of a magic link URL, then submit it along with their identity to sign in.How it works: The strategy derives a deterministic JWT ID from (strategy_name, user_subject, otp_code) via SHA-256. During request, it generates a random code, creates a JWT with that deterministic JTI, stores it in the existing TokenResource, and sends the short code to the user. During sign-in, it recomputes the JTI from the submitted code and looks it up — no new tables, actions, or schema changes to TokenResource needed.
Key features:
DSL example: