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

Use JWT + KV store instead of security_tokens table for #81

Open
apstanisic opened this issue Oct 8, 2023 · 0 comments
Open

Use JWT + KV store instead of security_tokens table for #81

apstanisic opened this issue Oct 8, 2023 · 0 comments

Comments

@apstanisic
Copy link
Owner

apstanisic commented Oct 8, 2023

Edit:
Maybe leave KV all togather, and use this solutions:

  • email change confirm. Add current and next email to jwt, and only change if both match
  • user invitation. We can generate password and display it to user. We will never have access to password + we'll recommend user to change it.
  • Sign Up. Ne need, just check if JWT is valid and confirm
  • Password reset. Add part of the hash to JWT https://stackoverflow.com/a/54865104
@apstanisic apstanisic changed the title Use Key Value store instead of security_tokens table for Use JWT + KV store instead of security_tokens table for Oct 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant