DEMO Initial passkey implementation #629
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
tombeckenham
temporarily deployed
to
development
GitHub Actions
Inactive
tombeckenham
changed the title
tombeckenham
temporarily deployed
to
development
GitHub Actions
Inactive
tombeckenham
temporarily deployed
to
development
GitHub Actions
Inactive
tombeckenham
temporarily deployed
to
development
GitHub Actions
Inactive
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.
Related Issue
Closes #264
Summary of Changes
This is a demo only, and we should discuss if we release this given the companies native passkey support - which would require the user recreate their wallet passkey.
Need Regression Testing
Risk Assessment
Security risks as we are encrypting and storing the user's password. There are also business risks as this implementation may impact native passkey support