KillingSpark / KillingSpark/Hadibar-Webapp
Auth Persistence
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Authentication info is currently stored only in the page's state. When the page is reloaded the user is not authenticated anymore.
By storing authentication information in the browser's session storage, authentication information would be persisted across reloads and the user remains logged-in for the duration of the browser session.
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Start by locating where authentication state is currently stored in the page, then trace the login and reload flow. Done means authentication survives a page reload and remains available for the browser session.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- authentication, frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100