Implement GET on /refresh #3

Closed
opened 2026-03-18 19:51:38 +00:00 by charlie · 0 comments
Owner

Summary

Implement the GET /refresh endpoint to allow clients to obtain a new JWT access token using a valid refresh token.

Behaviour

  1. Accept a valid refresh token (via Authorization header)
  2. Validate the refresh token
  3. On success, return:
    • Response body: A new JWT access token, and a new refresh token
  4. On failure, return an appropriate error

Acceptance Criteria

  • GET /refresh returns 200 with a new JWT in the response body
  • A new refresh token is returned in the response body
  • An expired or invalid refresh token returns 401
  • Old refresh token is invalidated after use
## Summary Implement the GET /refresh endpoint to allow clients to obtain a new JWT access token using a valid refresh token. ## Behaviour 1. Accept a valid refresh token (via Authorization header) 2. Validate the refresh token 3. On success, return: - Response body: A new JWT access token, and a new refresh token 4. On failure, return an appropriate error ## Acceptance Criteria - [x] GET /refresh returns 200 with a new JWT in the response body - [x] A new refresh token is returned in the response body - [x] An expired or invalid refresh token returns 401 - [x] Old refresh token is invalidated after use
charlie added this to the Working AUTH milestone 2026-03-18 19:51:38 +00:00
charlie self-assigned this 2026-03-18 19:51:38 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
ULFSII/phoenix_api#3
No description provided.