Reuse Existing Session from Secure Storage Instead of Re-Logging In

[tsutsu3]

Description

Currently, when a user logs in, a new session is created even if a valid session already exists in secure storage.
To improve user experience and reduce unnecessary resource usage, the system should check for an existing session during login and reuse it if valid, avoiding redundant re-authentication.

Motivation

• Resource Optimization: Reduce server-side resource usage by reusing existing sessions.
• Consistency: Ensures seamless transitions for users who restart the application or browser.

Proposed Solution

1. Check for Existing Session

   • During login, check secure storage (e.g., localStorage, sessionStorage, or a secure cookie) for an existing session token.
   • Validate the token against the server to ensure it is still active and has not expired.

2. Reuse the Session

   • If a valid session is found, bypass the login process and directly authenticate the user using the existing session.

3. Fallback to Login

   • If no valid session exists, proceed with the standard login process to create a new session.