idurar/idurar-erp-crm

Security improvement : refresh token (second token stored in localstorage)

Open

#204 opened on Jul 8, 2023

View on GitHub
 (11 comments) (0 reactions) (0 assignees)JavaScript (4,308 stars) (1,036 forks)batch import
good first issue🎨 Frontend🔧 Backend

Description

I think for better security and better user experience refresh tokens can be utilized.

Contributor guide

Tech stack
javascriptnodejsreactexpressmongodbrest api
Domain
backendsecurityauthentication
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
needs maintainer response
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
unclear
Prerequisites
basic understanding of JWTknowledge of Node.js authenticationfamiliarity with localStorage and cookies
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Investigate the current authentication flow in the backend, likely using JWT. Identify where tokens are generated and verified (e.g., in auth routes). Review existing comments in the issue (#204) for any discussion on implementation details. Propose a solution using a refresh token stored in an httpOnly cookie instead of localStorage for better security. Consider adding a token refresh endpoint and updating the frontend to handle token expiration.