การถอดรหัสและตรวจสอบ JWT

Welcome to this lesson! We'll explore how a Spring Security OAuth2 Resource Server automatically handles JSON Web Tokens (JWTs).

You'll learn about the decoding and validation processes that protect your API endpoints.

A Resource Server is an application that hosts protected resources (like API endpoints or data) and needs to verify who is trying to access them.

It relies on an Authorization Server to issue tokens (like JWTs) that grant access. The Resource Server then validates these tokens.

When a client wants to access a protected resource, it sends the JWT in the Authorization header of its HTTP request. This is typically done using the Bearer Token scheme.

• Bearer Token: A credential that grants access to anyone who possesses it.

The Resource Server extracts this token for processing.

When you configure a Spring Boot application as an OAuth2 Resource Server, Spring Security handles much of the JWT processing for you automatically.

It detects the Bearer token in the header and initiates its internal decoding and validation pipeline.

The first step is decoding the JWT. A JWT has three parts: Header, Payload, and Signature, separated by dots.

Decoding means parsing the base64-encoded Header and Payload into readable JSON. This step doesn't verify the token's authenticity yet; it just makes its content readable.

After decoding, the Resource Server performs crucial validation checks to ensure the JWT is legitimate and hasn't been tampered with. These checks include:

• Signature Verification: Is the token authentic?
• Expiration (exp): Is the token still valid?
• Not Before (nbf): Is the token active yet?
• Issuer (iss): Was it issued by the expected Authorization Server?
• Audience (aud): Is it intended for this Resource Server?

Signature verification is the most critical step. It ensures the token's integrity and authenticity.

The Resource Server uses the public key provided by the Authorization Server (or a shared secret for symmetric algorithms) to re-compute and compare the signature. If they don't match, the token is rejected.

Spring Security uses the JwtDecoder interface to perform the decoding and signature verification of a JWT. It takes the raw JWT string and returns a Jwt object, which contains the decoded headers and claims.

The most common implementation for JWS (JSON Web Signature) tokens is NimbusJwtDecoder.

To enable this automatic decoding and validation, you configure your Spring Boot application as an OAuth2 Resource Server. You typically provide the issuer URI or the JWK Set URI of your Authorization Server.

Spring Security will then fetch the public keys needed to verify incoming JWTs.

After a JWT is successfully decoded and validated, Spring Security converts its claims into an Authentication object, typically a JwtAuthenticationToken.

This object is then stored in the Security Context, making the user's principal (their identity) and granted authorities (permissions) available throughout the application.

Let's check your understanding of JWT validation. A Spring Security OAuth2 Resource Server performs several important checks to ensure a JWT is valid and trustworthy.

You've learned how a Spring Security OAuth2 Resource Server automatically decodes and validates JWTs!

• We covered the Resource Server's role in protecting resources.
• Explored how JWTs are received and automatically processed.
• Understood the critical steps of decoding, signature verification, and claim validation (expiration, issuer, audience).
• Saw how to configure the Resource Server to use an Authorization Server's JWK Set URI.
• Learned how validated JWTs populate the Security Context.

Next, we'll dive deeper into enforcing specific scopes and claims within incoming JWTs to control access to different parts of your API.