advancedScenario Questions

Scenario 15: A distributed system with resource servers across two data centers occasionally rejects valid, non-expired JWTs as 'expired' or 'not yet valid'.

This points to clock skew between servers — if the token-issuing Authorization Server's clock and a resource server's clock drift even a few seconds apart, strict exp/iat/nbf validation can incorrectly reject a technically-valid token. Fix by enabling NTP time synchronization across all servers and configuring a small, explicit clock-skew tolerance in the JWT validation library.

Ready to master this question?

Generate a complete walkthrough — background, the full answer in plain language, a working code example explained line by line, a real-world scenario, common mistakes, and how this same question gets asked in different ways.

Next Step

Continue to Scenario 16: Your monitoring detects the same refresh token being used from two different IP addresses within seconds of each other. →← Back to all Spring Security questions