Course contentsShow
← System Design
Lesson 946 of 1,91924. Authentication and Authorization at ScaleFree lesson

Token Refresh in Distributed Systems

Strategies for refreshing expired tokens across multiple services without disrupting user sessions.

Token Refresh in Distributed Systems

What you'll learn: How to seamlessly refresh expired authentication tokens across multiple services without interrupting active user sessions.

The Challenge

In distributed systems, access tokens typically have short lifespans (minutes to hours) for security. When a token expires mid-session, you need a strategy to refresh it across all services the user is interacting with—without forcing re-authentication or breaking active requests.

Core Strategies

1. Refresh Token Pattern with Central Service

The client holds a long-lived refresh token and exchanges it with an authorization server for new access tokens. When Service A receives a 401 (unauthorized), it can signal the client to refresh and retry—but the client orchestrates this, not individual services.

2. Token Refresh at API Gateway

The gateway intercepts expired token responses (401s from downstream), uses a stored refresh token (in secure storage), obtains a new access token, and retries the request transparently. The client never knows a refresh occurred.

3. Proactive Refresh

Rather than waiting for expiration, clients monitor token expiry (exp claim in JWTs) and refresh before making new requests. This prevents mid-request failures and eliminates retry logic complexity across services.

4. Refresh Token Rotation

For enhanced security, issue a new refresh token with each access token refresh. This limits the window for stolen refresh tokens and requires careful coordination—the client must store the latest refresh token atomically.

Coordination Pitfalls

Race conditions: Multiple services detecting expiration simultaneously can trigger parallel refresh attempts. Solution: client-side locking or idempotent refresh endpoints that recognize duplicate requests.

Token propagation delays: In service-to-service calls, ensure refreshed tokens cascade properly through the call chain, typically by updating headers in flight.

Key Takeaway: Token refresh in distributed systems requires choosing between client-orchestrated refresh (simple, transparent), gateway-managed refresh (client-invisible), or proactive refresh (prevents disruption)—each with distinct tradeoffs in complexity and user experience.