Create refresh_tokens Table for Persistent Sessions #29

Closed
opened 2025-10-17 23:20:05 +00:00 by Rodrigo2003-PT · 1 comment
Rodrigo2003-PT commented 2025-10-17 23:20:05 +00:00 (Migrated from github.com)

Securely store and manage refresh tokens.
Tasks:

  • Define the refresh_tokens table schema:
    • id (PK, UUID)
    • user_id (FK to users.id, Not Null)
    • token_hash (VARCHAR, Not Null, Unique)
    • expires_at (TIMESTAMPZ, Not Null)
    • is_revoked (BOOLEAN, default: false)
  • Create the database migration script.
  • Add a scheduled job to clean expired/revoked tokens.
Securely store and manage refresh tokens. Tasks: - Define the `refresh_tokens` table schema: - `id` (PK, UUID) - `user_id` (FK to `users.id`, Not Null) - `token_hash` (VARCHAR, Not Null, Unique) - `expires_at` (TIMESTAMPZ, Not Null) - `is_revoked` (BOOLEAN, default: false) - Create the database migration script. - Add a scheduled job to clean expired/revoked tokens.
Cordeir01 commented 2025-11-27 16:32:25 +00:00 (Migrated from github.com)

Refresh Tokens database logic done in the endpoints login/register issue

Refresh Tokens database logic done in the endpoints login/register issue
Sign in to join this conversation.
No description provided.