We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The Passkey-Button (Client side state) is awesome!
Still minor changes can be made to improve the AX and avoid user confusion.
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.
The text was updated successfully, but these errors were encountered:
incorbador
No branches or pull requests
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
Verification:
The text was updated successfully, but these errors were encountered: