Skip to content

fix: implement proper JWT token expiration check#3

Merged
dipak0000812 merged 1 commit intodipak0000812:mainfrom
Prachipingale0205:fix-token-expiry
Jan 25, 2026
Merged

fix: implement proper JWT token expiration check#3
dipak0000812 merged 1 commit intodipak0000812:mainfrom
Prachipingale0205:fix-token-expiry

Conversation

@Prachipingale0205
Copy link
Collaborator

Description

This PR fixes incorrect token expiration handling in the frontend.

The previous implementation always returned false, which caused the frontend to treat all tokens as valid indefinitely.

This change:

  • Implements JWT exp claim–based expiration checking
  • Treats invalid or malformed tokens as expired
  • Aligns frontend session behavior with backend security enforcement

Related Issue

Fixes #2

Type of Change

  • Bug fix (non-breaking change that fixes an issue)
  • Security fix

@vercel
Copy link

vercel bot commented Jan 24, 2026

@Prachipingale0205 is attempting to deploy a commit to the Dipak's projects Team on Vercel.

A member of the Team first needs to authorize it.

Copy link
Owner

@dipak0000812 dipak0000812 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Fix correctly restores JWT expiration handling on the frontend.

@dipak0000812 dipak0000812 merged commit 3be9814 into dipak0000812:main Jan 25, 2026
2 of 9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Token expiration check disabled in frontend

2 participants