[Draft] No passkey demo #49
Draft
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
This updates the interface so a passkey isn't required and samples creating a key
still need key export, but has an idea
still missing lots of UI parts, but not bad for some AI
Use mnemonic so it's a little easier to manage the non encrpyted version
|
Visit the preview URL for this PR (updated for commit 1c3c383): https://zksync-auth-server-staging--pr49-no-passkey-demo-sxqpl9a5.web.app (expires Wed, 12 Feb 2025 03:23:34 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: 509a9c9ea42583076f531c53cf2979c544d5d0b7 |
Still requires some server setup to provide the iv + salt
Still have test errors, probably related to parsing
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.
Description
We're looking to support owner keys that aren't passkey based in case the platform or user can't use passkeys
The contracts support this, but there are some small improvements that we can make to the SDK to better enable this.
Additional context
Depending on the use case (security vs ease of recovery), an embedded application may choose one of the 3 paths: