lynndylanhurley / lynndylanhurley/devise_token_auth
Where to store token securely?
Open
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 3.6k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
I have been review this https://github.com/lynndylanhurley/devise_token_auth/issues/1005 the answer in this issue is not correct. We need to guide the way to handle token securely on client side. Nothing I know from this gem to store token securely.
I think the better way is to handle token with HttpOnly cookie
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start by reviewing the linked issue 1005 and the current client-side token guidance, then determine whether HttpOnly cookies should be the recommended approach; done means the project has clear, security-accurate guidance for storing tokens on the client.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rails, ruby
- Domain
- api, authentication, security
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100