sahat/megaboilerplate

React: user cookie should be cleared if user no longer exists

Open

#155 opened on Jul 7, 2016

View on GitHub
 (1 comment) (0 reactions) (0 assignees)CSS (3,830 stars) (273 forks)batch import
BugHelp Wanted

Description

If a user has been manually deleted from the database or no longer exists for whatever reason, a cookie - that normally gets deleted during logout - should be automatically cleared from the Browser.

screenshot 2016-07-06 17 57 57

Contributor guide

Tech stack
reactjavascript
Domain
frontendsecurity
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.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Reactcookie handlingauthentication flow
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Investigate the React starter project in sahat/megaboilerplate to understand how authentication cookies are currently set and cleared. Likely, there is a login/logout mechanism that sets a cookie with user data. On application load or periodic API calls, check if the user still exists on the backend; if not, clear the cookie client side. Look for existing cookie utility functions and authentication context providers.