-
Notifications
You must be signed in to change notification settings - Fork 22
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
validation phrase for email security #688
Comments
I think for both #1 and #2, we may need to think from a clean slate about what is appropriate for the #1 or #2 may be solved for in different ways, so might also be good to make them two distinct issues and we prioritize one above the other (and so we can discuss one in isolation from the other). |
Yep that's true, though from a user perspective not much has changed here - I'd probably need to copy the phrase generation code into the I do think we need to think about these from a clean slate though, especially given the UX changes @Gozala has been advocating for around capability grants - if we're going to have a more complicated UX after the user clicks on the email (in which they can select which capabilities they want to grant) we'll need to think about where this sort of thing fits in that UX. |
Purpose of this ticket:
The text was updated successfully, but these errors were encountered: