Belirteç Güvenliği (Erişim/Yenileme)

Welcome to Token Security! In this lesson, we'll dive into protecting the vital components of OAuth2 and OpenID Connect: access tokens and refresh tokens.

These tokens are like digital keys. If they fall into the wrong hands, unauthorized access to your users' data or your application's resources can occur. Securing them is paramount.

Access tokens are credentials that grant a client application permission to access specific resources on behalf of the user. Think of them as a temporary pass.

• They have a short lifespan (minutes to hours).
• They are used directly to authorize API requests.
• If compromised, the damage is limited due to their short expiry.

Refresh tokens are used to obtain new access tokens after the current one expires, without requiring the user to re-authenticate. They are like a master key.

• They have a much longer lifespan (days, weeks, or even months).
• They are highly sensitive because their compromise can grant continuous access.
• They should be stored with the highest level of security.

The most fundamental rule for token security is to always transmit tokens over HTTPS (TLS). This encrypts the communication channel between the client and the server.

Without HTTPS, tokens sent over an unsecured network (like public Wi-Fi) could be easily intercepted by attackers, leading to immediate compromise.

Access tokens, due to their short lifespan, require careful client-side storage:

• Web Applications: Store in memory (JavaScript variables) or secure, httpOnly cookies. Avoid localStorage or sessionStorage due to XSS vulnerability.
• Mobile Applications: Use platform-specific secure storage like iOS Keychain or Android Keystore.

Access tokens are designed to expire. This code snippet shows a conceptual way to check if a token, represented by its issue and expiry times, is still valid.

Refresh tokens are the most critical to protect due to their long lifespan. Their storage must be even more stringent:

• Web Applications: Exclusively use httpOnly, secure cookies. Never store in JavaScript-accessible storage.
• Mobile Applications: Utilize hardware-backed secure storage (e.g., Secure Enclave on iOS, TEE on Android) if available.

Refresh Token Rotation (RTR) is a crucial security enhancement. Each time a client uses a refresh token to get a new access token, the authorization server should issue a new refresh token and invalidate the old one.

If an old refresh token is stolen and used, the legitimate client will detect it because its current refresh token will no longer work, signaling a potential breach.

Tokens should not just expire; they should also be revocable. The authorization server must provide mechanisms to invalidate tokens prematurely.

• User Logout: All associated access and refresh tokens should be revoked.
• Password Change: Revoke all active tokens to force re-authentication.
• Suspicious Activity: If a token is suspected of being compromised, it should be immediately revoked.

Balancing security and user experience is key:

• Access Tokens: Keep their lifespan short (e.g., 5-15 minutes). This limits the window of opportunity for attackers if a token is compromised.
• Refresh Tokens: Can have longer lifespans (e.g., 7-30 days), but must be revocable and ideally protected with RTR.

Which of the following are recommended best practices for securing OAuth2/OIDC tokens?

You've learned the critical practices for securing access and refresh tokens!

• HTTPS/TLS is non-negotiable for transmission.
• Access tokens need secure, short-lived storage (memory, httpOnly cookies).
• Refresh tokens demand the highest security (httpOnly, secure cookies, hardware-backed storage) and should use Refresh Token Rotation.
• Implement effective revocation strategies and manage token lifespans wisely.