Implement Refresh Token Mechanism for Persistent Sessions #160

Merged
Cordeir01 merged 3 commits from implement_refresh_token into main 2025-12-11 17:17:51 +00:00
Cordeir01 commented 2025-12-09 17:42:29 +00:00 (Migrated from github.com)

Allows us to keep access_tokens short-lived while allowing users to maintain a persistent session without re-entering their credentials. This flow involves issuing a long-lived, single-use refresh_token that is stored securely in the database (hashed) and can be exchanged for a new, short-lived access_token.

closes #28

Allows us to keep access_tokens short-lived while allowing users to maintain a persistent session without re-entering their credentials. This flow involves issuing a long-lived, single-use refresh_token that is stored securely in the database (hashed) and can be exchanged for a new, short-lived access_token. closes #28
AndreFerreira5 (Migrated from github.com) reviewed 2025-12-09 17:42:29 +00:00
Rodrigo2003-PT (Migrated from github.com) approved these changes 2025-12-11 17:17:01 +00:00
Rodrigo2003-PT (Migrated from github.com) left a comment

The code looks consistent and well aligned with the fundamental operation requested in the parent issue:
" Implement Refresh Token Mechanism for Persistent Sessions #160 "

The code looks consistent and well aligned with the fundamental operation requested in the parent issue: " Implement Refresh Token Mechanism for Persistent Sessions #160 "
Sign in to join this conversation.
No description provided.