Open
Conversation
Deploying passkeys-dev with
|
| Latest commit: |
587a9ed
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://01e62314.passkeys-dev.pages.dev |
| Branch Preview URL: | https://mm-requirements-backend.passkeys-dev.pages.dev |
Contributor
Author
|
This will probably also end up addressing #131 at the same time. |
Closed
9d0dc54 to
20c75ed
Compare
timcappalli
reviewed
Jan 3, 2025
652a508 to
689cb5c
Compare
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.
This PR adds guidance on what the backend's responsibilities are in facilitating passkey registration and authentication. Code samples are in TypeScript, but primarily as a way to communicate typings that are hopefully easy to map to other languages.
Everything so far is "vanilla JS" (i.e. I don't suggest using something like SimpleWebAuthn, even though it's still possible as per previous conversations) which is why there are a couple of
TODOs still in this PR.I've also added a placeholder implementation page for the frontend so that I can link to it when the backend requirements transition into frontend requirements.
Fixes #152.