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.

Sign up for GitHub

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

Jump to bottom

Authentication next steps #62

Open
8 tasks
Frando opened this issue Aug 5, 2020 · 0 comments
Open
8 tasks

Authentication next steps #62

Frando opened this issue Aug 5, 2020 · 0 comments

Comments

@Frando
Copy link
Member

Frando commented Aug 5, 2020 •
edited
Loading

What we still need to do:

  • client: don't store tokens/accesscode in localStorage, use secure cookies instead
  • server: allow to create tokens with read/write capabilities for specific collections
  • client: support multiple tokens/accesscodes
  • rethink token vs accesscode model, review where we want/need JWTs
  • add one-time login links for use in short URLs, remove accesscodes
  • maybe add sessions (after login) with plain old session cookies (less overhead than JWTs in all requests)
  • add UI to manage tokens
  • rethink if/how we want to derive tokens/JWT from hypercore keys
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Frando