Integrasi AuthenticationManager dan Penyedia
Hubungkan filter JWT Anda dengan `AuthenticationManager` milik Spring Security dan penyedia autentikasi kustom.
Integrasi AuthenticationManager dan Penyedia adalah pelajaran Spring Security 6 & JWT Authentication gratis di CoddyKit. Ini adalah pelajaran 3 dari 4. Kamu bisa membaca pelajaran lengkapnya di bawah secara gratis — lalu praktikkan langsung di browser dengan editor kode bawaan dan tutor AI 24/7. Ini adalah bagian dari jalur belajar Spring Security 6 & JWT Authentication, dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus Spring Security 6 & JWT Authentication mencakup 4 pelajaran total.
Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.
Orchestrating Authentication
Welcome to the core of Spring Security's authentication process! Today, we'll connect our JWT filter with two vital components: the AuthenticationManager and AuthenticationProvider.
These components work together to verify a user's identity and establish their security context.
The Manager's Core Responsibility
The AuthenticationManager is the central interface in Spring Security for handling authentication requests. Think of it as the conductor of an orchestra.
- It receives an
Authenticationobject (representing a user's credentials). - It delegates the actual authentication task to one or more
AuthenticationProviders. - If successful, it returns a fully authenticated
Authenticationobject.
The Role of AuthenticationProvider
While the AuthenticationManager orchestrates, AuthenticationProviders are the specialized workers.
Each provider knows how to authenticate a specific type of user or credential (e.g., username/password, LDAP, or in our case, a JWT). It contains the logic to validate the credentials.
Crafting a JWT Token Object
For our JWT flow, we need a way to represent an unauthenticated JWT within Spring Security. We'll create a custom Authentication implementation, often called JwtAuthenticationToken.
- It will hold the raw JWT string when unauthenticated.
- After authentication, it will hold the authenticated user's details (
UserDetails) and authorities.
Building Our JWT Provider
Now, let's create our own JwtAuthenticationProvider. This class will implement the AuthenticationProvider interface.
Its main job is to take our JwtAuthenticationToken, validate the JWT, extract user details, and return a fully authenticated token.
JwtAuthenticationProvider Logic
Here's a simplified look at what our JwtAuthenticationProvider's authenticate method might do. It checks if the token is valid and then builds an authenticated object.
import org.springframework.security.authentication.AuthenticationProvider;
import org.springframework.security.core.Authentication;
import org.springframework.security.core.AuthenticationException;
import org.springframework.security.core.userdetails.User;
import org.springframework.security.core.GrantedAuthority;
import java.util.Collections;
public class CustomJwtAuthProvider implements AuthenticationProvider {
@Override
public Authentication authenticate(Authentication authentication)
throws AuthenticationException {
// In a real app, you'd validate the JWT here.
// For this example, we'll assume it's valid if it's our custom type.
if (authentication instanceof JwtAuthenticationToken) {
// Simulate successful JWT validation
// Extract username and roles from the JWT payload
String username = "coddykitUser"; // From JWT subject
// Roles would also come from JWT claims
// For simplicity, we grant a basic role
GrantedAuthority role = () -> "ROLE_USER";
User userDetails = new User(username, "", Collections.singletonList(role));
// Return a fully authenticated token
// The credentials (JWT string) are usually cleared
return new JwtAuthenticationToken(userDetails, Collections.singletonList(role));
}
return null; // Not our type of authentication
}
@Override
public boolean supports(Class<?> authentication) {
// This provider supports our custom JwtAuthenticationToken
return JwtAuthenticationToken.class.isAssignableFrom(authentication);
}
// Simple placeholder for our custom token
static class JwtAuthenticationToken implements Authentication {
private final User userDetails;
private final String jwtToken;
private boolean authenticated;
private java.util.Collection<? extends GrantedAuthority> authorities;
public JwtAuthenticationToken(String jwtToken) {
this.jwtToken = jwtToken;
this.userDetails = null;
this.authenticated = false;
this.authorities = Collections.emptyList();
}
public JwtAuthenticationToken(User userDetails,
java.util.Collection<? extends GrantedAuthority> authorities) {
this.userDetails = userDetails;
this.jwtToken = null; // Token already validated
this.authenticated = true;
this.authorities = authorities;
}
@Override
public java.util.Collection<? extends GrantedAuthority> getAuthorities() {
return authorities;
}
@Override
public Object getCredentials() {
return jwtToken; // The raw JWT string (if unauthenticated)
}
@Override
public Object getDetails() {
return userDetails;
}
@Override
public Object getPrincipal() {
return userDetails; // The authenticated user object
}
@Override
public boolean isAuthenticated() {
return authenticated;
}
@Override
public void setAuthenticated(boolean isAuthenticated)
throws IllegalArgumentException {
this.authenticated = isAuthenticated;
}
@Override
public String getName() {
return userDetails != null ? userDetails.getUsername() : "N/A";
}
}
public static void main(String[] args) {
System.out.println("CustomJwtAuthProvider initialized.");
// In a real app, Spring Security would call authenticate()
// We're just demonstrating the class structure here.
}
}Wiring Up the Provider
For our JwtAuthenticationProvider to be used, we must register it with Spring Security's configuration. This is typically done in your security configuration class.
Spring Boot often auto-configures the AuthenticationManager, but we can add custom providers to it.
Filter-Manager Interaction
Remember our custom JwtAuthenticationFilter from the previous lesson? Now we connect it to the AuthenticationManager.
- The filter will extract the JWT from the request.
- It will create an unauthenticated
JwtAuthenticationToken. - It will then pass this token to the
AuthenticationManagerfor processing.
The manager, in turn, will find and use our JwtAuthenticationProvider.
JWT Authentication Journey
Let's trace the full authentication flow with our new components:
- Client sends request with JWT in the
Authorizationheader. - Our
JwtAuthenticationFilterintercepts the request, extracts the JWT. - Filter creates an unauthenticated
JwtAuthenticationToken. - Filter calls
AuthenticationManager.authenticate()with this token. AuthenticationManagerfinds ourJwtAuthenticationProvider(becausesupports()returns true).JwtAuthenticationProvidervalidates the JWT and builds a fully authenticatedJwtAuthenticationToken(containingUserDetailsand authorities).- The filter receives the authenticated token and sets it in the
SecurityContextHolder. - The request proceeds, now knowing who the user is and what they can do!
Understanding the Flow
Which statements accurately describe the roles of AuthenticationManager and AuthenticationProvider in a Spring Security JWT setup?
Bringing It All Together
In this lesson, we've explored how AuthenticationManager acts as the central orchestrator and how a custom AuthenticationProvider handles the specific logic for validating JWTs.
By integrating these components with our JwtAuthenticationFilter, we've established a robust and modular JWT authentication flow within Spring Security. This separation of concerns makes your security configuration flexible and maintainable!
Belajar Java dengan tutor AI — gratis
Tulis dan jalankan kode asli di browser kamu, dapatkan bantuan instan dari tutor AI 24/7, dan lanjutkan di mana kamu tinggalkan di web atau aplikasi.
- Kursus
- 12
- Pelajaran
- 48
Pertanyaan yang Sering Diajukan
Apakah pelajaran “Integrasi AuthenticationManager dan Penyedia” gratis?
Ya — teks lengkap “Integrasi AuthenticationManager dan Penyedia” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus Spring Security 6 & JWT Authentication, upgrade ke CoddyKit PRO. Kursus Spring Security 6 & JWT Authentication mencakup 4 pelajaran total.
Apa yang akan aku pelajari di “Integrasi AuthenticationManager dan Penyedia”?
Hubungkan filter JWT Anda dengan `AuthenticationManager` milik Spring Security dan penyedia autentikasi kustom. Kamu berlatih Spring Security 6 & JWT Authentication dengan kode praktik yang langsung kamu jalankan di browser, dan tutor AI 24/7 menjawab pertanyaanmu saat kamu mengerjakan pelajaran ini.
Apakah aku perlu pengalaman untuk memulai Spring Security 6 & JWT Authentication?
Tidak diperlukan pengalaman sebelumnya. Spring Security 6 & JWT Authentication di CoddyKit dirancang untuk pemula hingga pelajar tingkat lanjut, jadi kamu bisa memulai di sini atau dari awal dan belajar sesuai kecepatan kamu sendiri. Ini adalah pelajaran 3 dari 4.
Berapa lama pelajaran “Integrasi AuthenticationManager dan Penyedia” memakan waktu?
Sebagian besar pelajaran CoddyKit memakan waktu sekitar 5–10 menit. Setiap pelajaran ringkas dan interaktif, jadi kamu membuat kemajuan stabil dan melanjutkan dari tempat kamu tinggalkan di web dan aplikasi.
Bisakah aku menulis dan menjalankan kode dalam pelajaran Spring Security 6 & JWT Authentication ini?
Ya. Setiap pelajaran Spring Security 6 & JWT Authentication menyertakan editor kode bawaan, jadi kamu menulis dan menjalankan kode nyata langsung di browser dan mendapatkan umpan balik AI instan — tidak diperlukan penyiapan lokal.
Semua pelajaran dalam kursus ini
- Merancang Alur Autentikasi JWT
- Menerapkan Penyaring JWT Kustom
- Integrasi AuthenticationManager dan Penyedia
- Menangani Kesalahan Autentikasi dan Titik Masuk