Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve passkey-button logic #371

Open
4 tasks
Adam3371 opened this issue May 22, 2024 · 0 comments
Open
4 tasks

Improve passkey-button logic #371

Adam3371 opened this issue May 22, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@Adam3371
Copy link
Contributor

Why

The Passkey-Button (Client side state) is awesome!

Still minor changes can be made to improve the AX and avoid user confusion.

TODOS

Ensure that with the identifier used in the Client side state it is always possible to log in.

Currently it is not possible to use the identififier saved in client side state if:

  • Identifier is changed during the signup process

  • Email and Phone are activated but only phone is verified. (Client side state saves email)

  • If a identifier is edited during the signup process, save the updated identifier in the client side state

  • Always save the primary identifier of a user in the client side state.

Acceptance criteria

  • Changing identifier during signup saves the updated identifier.
  • Signup with following settings makes it possible to use the passkey button
    Verification:
  • Email: at first login
  • Phone: at signup
@Adam3371 Adam3371 added the enhancement New feature or request label May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants