Skip to content

Implement Refresh Token Mechanism #31

Open
Open
Implement Refresh Token Mechanism#31
Assignees
JinxSeven
Labels
backendBackend API endpoints, contracts, or integrationsfrontendFrontend core logical operationsimportantImportant but not urgent; should be in the next planned cycleprotectionSecurity setup, vulnerabilities or fortifying
@JinxSeven

Description

@JinxSeven
JinxSeven
opened on Mar 28, 2026

Refresh Token and Logout Endpoints

Expected Outcome:

  • Deepen the understanding on refresh token mechanism
  • Implementation in both backend and frontend
  • Test its working

Metadata

Metadata

Assignees

Labels

backendBackend API endpoints, contracts, or integrationsfrontendFrontend core logical operationsimportantImportant but not urgent; should be in the next planned cycleprotectionSecurity setup, vulnerabilities or fortifying

Projects

ChMS

Status

In progress

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions