Spring Security 6 & JWT Authentication · 课时

自定义身份验证事件处理

为身份验证成功和失败事件创建自定义监听器，以实现日志记录、审计或其他操作。

自定义身份验证事件处理 是 CoddyKit 上的免费 Spring Security 6 & JWT Authentication 课时。这是第 3 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 Spring Security 6 & JWT Authentication 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Spring Security 6 & JWT Authentication 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

Intro to Auth Events

Welcome to Custom Authentication Event Handling! In Spring Security, many important actions, like a user logging in or failing to log in, trigger events.

These events are like signals that your application can 'listen' for. By listening, you can react to these security-related happenings.

Logging: Record who logged in and when.
Auditing: Track security-sensitive actions.
Custom Logic: Implement specific actions on success or failure (e.g., lock accounts after too many failed attempts).

Spring's Event System

Spring Framework has a powerful event publication and subscription model. Spring Security leverages this to publish various authentication-related events.

You can create custom components that 'listen' for these events and execute logic whenever they occur. This keeps your security logic separate and clean.

Key Authentication Events

Two of the most common and useful authentication events you'll encounter are:

AuthenticationSuccessEvent: Fired when a user successfully authenticates. This is perfect for logging successful logins or updating last login times.
AbstractAuthenticationFailureEvent: This is a base class for all authentication failure events. Specific failure types (e.g., bad credentials, disabled account) extend this. You can listen to the base class to catch all failures or specific subclasses.

Creating a Custom Listener

To create a listener, you typically use the @EventListener annotation on a method within a Spring component. Spring automatically detects these methods and registers them as event listeners.

The method's parameter type determines which event it will listen to. For example, a method with an AuthenticationSuccessEvent parameter will only be called when that specific event occurs.

Code: Success Listener Setup

Let's set up a simple Spring Boot application with in-memory authentication. This will allow us to trigger authentication events and see our listeners in action.

import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.context.annotation.Bean;
import org.springframework.security.config.annotation.web.builders.HttpSecurity;
import org.springframework.security.config.annotation.web.configuration.EnableWebSecurity;
import org.springframework.security.core.userdetails.User;
import org.springframework.security.core.userdetails.UserDetails;
import org.springframework.security.core.userdetails.UserDetailsService;
import org.springframework.security.provisioning.InMemoryUserDetailsManager;
import org.springframework.security.web.SecurityFilterChain;

@SpringBootApplication
@EnableWebSecurity
public class EventHandlingApp {

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

    @Bean
    public UserDetailsService userDetailsService() {
        UserDetails user = User.withDefaultPasswordEncoder()
            .username("user")
            .password("password")
            .roles("USER")
            .build();
        return new InMemoryUserDetailsManager(user);
    }

    @Bean
    public SecurityFilterChain securityFilterChain(HttpSecurity http) throws Exception {
        http
            .authorizeHttpRequests(auth -> auth
                .anyRequest().authenticated()
            )
            .formLogin();
        return http.build();
    }
}

Code: Implementing Success Listener

Now, let's create our custom listener for successful authentication. We'll simply log a message when a user successfully logs in.

Save this as a new Java file (e.g., AuthenticationSuccessListener.java) in the same package as EventHandlingApp. Then, run EventHandlingApp and try to log in via a browser (e.g., localhost:8080 with user/password).

import org.springframework.context.event.EventListener;
import org.springframework.security.authentication.event.AuthenticationSuccessEvent;
import org.springframework.stereotype.Component;

@Component
public class AuthenticationSuccessListener {

    @EventListener
    public void handleAuthenticationSuccess(AuthenticationSuccessEvent event) {
        String username = event.getAuthentication().getName();
        System.out.println("SUCCESS: User '" + username + "' logged in successfully!");
        // You could also log full details, update a database, etc.
    }
}

Handling Authentication Failures

Just as important as successful logins are failed attempts. Spring Security provides AbstractAuthenticationFailureEvent and its subclasses to handle these scenarios.

By listening to this event, you can:

Log failed attempts for security auditing.
Implement brute-force protection (e.g., locking an account after N failures).
Trigger alerts for suspicious activity.

Code: Implementing Failure Listener

Let's add a listener for authentication failures. This listener will catch any type of failure and log the username and the reason for the failure.

Add this as another @Component or as a method in your existing AuthenticationSuccessListener. Try logging in with incorrect credentials to see it in action.

import org.springframework.context.event.EventListener;
import org.springframework.security.authentication.event.AbstractAuthenticationFailureEvent;
import org.springframework.stereotype.Component;

@Component
public class AuthenticationFailureListener {

    @EventListener
    public void handleAuthenticationFailure(AbstractAuthenticationFailureEvent event) {
        String username = event.getAuthentication().getName();
        String failureReason = event.getException().getMessage();
        System.err.println("FAILURE: User '" + username + "' failed to log in. Reason: " + failureReason);
        // You can check event.getException() for specific failure types
    }
}

Distinguishing Failure Types

AbstractAuthenticationFailureEvent is a parent class. For more granular control, you can listen to specific subclasses:

BadCredentialsEvent: Incorrect username/password.
DisabledExceptionEvent: User account is disabled.
LockedExceptionEvent: User account is locked.
AccountExpiredExceptionEvent: User account has expired.

You can create separate @EventListener methods for each or use instanceof checks within a single listener.

Custom Event Handling Check

You've learned how to create listeners for Spring Security authentication events. Let's check your understanding.

Recap: Event Handling

We've covered how Spring Security leverages Spring's event system to publish authentication-related events. You learned to:

Understand the purpose of authentication events for logging and auditing.
Use the @EventListener annotation to create custom listeners.
Handle AuthenticationSuccessEvent for successful logins.
Handle AbstractAuthenticationFailureEvent for various login failures.

By using these events, you gain powerful control and visibility into your application's authentication process.

常见问题解答

「自定义身份验证事件处理」课时是免费的吗？

是的 — 「自定义身份验证事件处理」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Spring Security 6 & JWT Authentication 课程的其余内容，请升级到 CoddyKit PRO。 Spring Security 6 & JWT Authentication 课程共包含 4 节课。

「自定义身份验证事件处理」这节课中我会学到什么？

为身份验证成功和失败事件创建自定义监听器，以实现日志记录、审计或其他操作。你通过在浏览器中直接运行的动手代码来练习 Spring Security 6 & JWT Authentication，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 Spring Security 6 & JWT Authentication 需要有经验吗？

无需任何先前经验。CoddyKit 上的 Spring Security 6 & JWT Authentication 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 3 节课，共 4 节。

「自定义身份验证事件处理」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 Spring Security 6 & JWT Authentication 课中编写并运行代码吗？

能。每节 Spring Security 6 & JWT Authentication 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 Spring Security 6 & JWT Authentication