Spring Security 6 & JWT Authentication · Lezione

Configurazione del Resource Server

Configuri un'applicazione Spring Boot come OAuth2 Resource Server per proteggere gli endpoint della sua API.

Configurazione del Resource Server è una lezione Spring Security 6 & JWT Authentication gratuita su CoddyKit. Questa è la lezione 1 di 4. Puoi leggere la lezione completa qui gratuitamente — poi esercitati direttamente nel browser con un editor di codice integrato e un tutor IA disponibile 24/7. Fa parte del percorso di apprendimento Spring Security 6 & JWT Authentication, e i tuoi progressi si sincronizzano tra il web e l'app CoddyKit. Il corso Spring Security 6 & JWT Authentication include 4 lezioni in totale.

Parti di questa lezione non sono ancora state tradotte e vengono mostrate in inglese.

What is a Resource Server?

Welcome to configuring a Spring Security OAuth2 Resource Server! This is a crucial component in modern secure applications.

A Resource Server hosts protected resources, like your API endpoints.
It receives access tokens from clients and validates them.
If a token is valid, it grants access to the requested resource.

Think of it as the bouncer at a club, checking tickets (access tokens) before letting anyone in.

Role in OAuth2 Flow

In the OAuth2 flow, the Resource Server works hand-in-hand with an Authorization Server.

The client first gets an access token from the Authorization Server.
Then, the client sends this token to the Resource Server when requesting a protected resource.
The Resource Server doesn't issue tokens; it only validates them.

This separation of concerns makes your application more secure and scalable.

Essential Dependencies

To turn your Spring Boot application into an OAuth2 Resource Server, you need a specific dependency.

The key dependency is spring-boot-starter-oauth2-resource-server. This starter brings in all the necessary Spring Security components to handle OAuth2 access tokens.

It simplifies the setup process by providing auto-configuration for common scenarios.

Adding the Dependency

Let's add the required dependency to your project's pom.xml (for Maven users) or build.gradle (for Gradle users).

For Maven, place this inside your <dependencies> block:

<dependency>
  <groupId>org.springframework.boot</groupId>
  <artifactId>spring-boot-starter-oauth2-resource-server</artifactId>
</dependency>

Enabling Resource Server Security

With the dependency in place, we need to configure Spring Security. In Spring Security 6, this is typically done using a SecurityFilterChain bean.

This configuration tells Spring Security to treat incoming requests as if they might contain an OAuth2 access token.

Basic Security Filter Chain

Here's a minimal Java configuration for enabling the Resource Server:

The oauth2ResourceServer().jwt() part tells Spring Security to expect JWTs (JSON Web Tokens) as access tokens.

import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;
import org.springframework.security.config.annotation.web.builders.HttpSecurity;
import org.springframework.security.web.SecurityFilterChain;

@Configuration
public class SecurityConfig {

  @Bean
  public SecurityFilterChain securityFilterChain(HttpSecurity http) throws Exception {
    http
      .authorizeHttpRequests(authorize -> authorize
        .anyRequest().authenticated()
      )
      .oauth2ResourceServer(oauth2 -> oauth2.jwt());
    return http.build();
  }
}

Configuring JWT Source

For the Resource Server to validate JWTs, it needs to know where to find the public keys or how to introspect the token.

You configure this in your application.properties or application.yml file. The most common way is to provide the JWK Set URI or the Issuer URI.

JWK Set URI (jwk-set-uri): Points to an endpoint where the Authorization Server publishes its public keys (JSON Web Key Set).
Issuer URI (issuer-uri): Points to the Authorization Server's base URL, from which the JWK Set URI can be discovered.

Setting JWK Set URI

Let's add the jwk-set-uri to our application.properties. This URI is provided by your Authorization Server.

Replace http://auth-server/realms/master/protocol/openid-connect/certs with the actual URI from your Authorization Server.

spring.security.oauth2.resourceserver.jwt.jwk-set-uri=http://auth-server/realms/master/protocol/openid-connect/certs

Creating a Protected Endpoint

Now, let's create a simple REST endpoint that our Resource Server will protect. Only requests with a valid access token will be able to reach this endpoint.

We'll use a basic @RestController for this.

import org.springframework.web.bind.annotation.GetMapping;
import org.springframework.web.bind.annotation.RestController;

@RestController
public class ProtectedController {

  @GetMapping("/api/hello")
  public String hello() {
    return "Hello, secured world!";
  }
}

Putting It All Together

Here's a full, runnable Spring Boot application demonstrating a minimal Resource Server setup with a protected endpoint. Remember to update the jwk-set-uri in application.properties!

When you run this, try accessing /api/hello without a token (you'll get 401 Unauthorized).

import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;
import org.springframework.security.config.annotation.web.builders.HttpSecurity;
import org.springframework.security.web.SecurityFilterChain;
import org.springframework.web.bind.annotation.GetMapping;
import org.springframework.web.bind.annotation.RestController;

@SpringBootApplication
public class ResourceServerApplication {

  public static void main(String[] args) {
    SpringApplication.run(ResourceServerApplication.class, args);
  }

  @Configuration
  public static class SecurityConfig {
    @Bean
    public SecurityFilterChain securityFilterChain(HttpSecurity http) throws Exception {
      http
        .authorizeHttpRequests(authorize -> authorize
          .anyRequest().authenticated()
        )
        .oauth2ResourceServer(oauth2 -> oauth2.jwt());
      return http.build();
    }
  }

  @RestController
  public static class ProtectedController {
    @GetMapping("/api/hello")
    public String hello() {
      return "Hello, secured world!";
    }
  }
}

Resource Server Purpose Check

Which of the following best describes the primary role of an OAuth2 Resource Server?

Recap: Resource Server Setup

Great job! You've learned the fundamentals of setting up an OAuth2 Resource Server.

We understood that a Resource Server protects APIs by validating access tokens.
We added the spring-boot-starter-oauth2-resource-server dependency.
We configured a SecurityFilterChain to enable JWT-based resource server security.
We learned how to specify the JWT source (e.g., jwk-set-uri) in application.properties.

Next, we'll dive deeper into how the Resource Server decodes and validates these JWTs.

Domande Frequenti

La lezione «Configurazione del Resource Server» è gratuita?

Sì — il testo completo di «Configurazione del Resource Server» è gratuito qui sul web. Per esercitarvi in modo interattivo (un editor di codice integrato e un tutor IA 24/7) e sbloccare il resto del corso Spring Security 6 & JWT Authentication, passa a CoddyKit PRO. Il corso Spring Security 6 & JWT Authentication include 4 lezioni in totale.

Cosa imparerò in «Configurazione del Resource Server»?

Configuri un'applicazione Spring Boot come OAuth2 Resource Server per proteggere gli endpoint della sua API. Eserciti Spring Security 6 & JWT Authentication con codice pratico che esegui direttamente nel browser, e un tutor IA 24/7 risponde alle tue domande mentre lavori sulla lezione.

Ho bisogno di esperienza per iniziare Spring Security 6 & JWT Authentication?

Non è richiesta alcuna esperienza precedente. Spring Security 6 & JWT Authentication su CoddyKit è strutturato per principianti e studenti avanzati, quindi puoi iniziare da qui o dall'inizio e procedere al tuo ritmo. Questa è la lezione 1 di 4.

Quanto tempo richiede la lezione «Configurazione del Resource Server»?

La maggior parte delle lezioni CoddyKit richiede circa 5–10 minuti. Ogni lezione è breve e interattiva, quindi fai progressi costanti e riprendi esattamente da dove hai lasciato su web e app.

Posso scrivere ed eseguire codice in questa lezione Spring Security 6 & JWT Authentication?

Sì. Ogni lezione Spring Security 6 & JWT Authentication include un editor di codice integrato, quindi scrivi ed esegui codice reale direttamente nel tuo browser e ricevi feedback istantaneo dall'IA — nessuna configurazione locale necessaria.

Tutte le lezioni di questo corso

Configurazione del Resource Server
Decodifica e convalida dei JWT
Applicazione di scope e claim
Mappare i claim JWT sulle autorità di Spring

← Torna a Spring Security 6 & JWT Authentication