1
1
[[servlet-events]]
2
2
== Authentication Events
3
3
4
- For each authentication that succeeds or fails, a `AuthenticationSuccessEvent` or `AuthenticationFailureEvent ` is fired, respectively.
4
+ For each authentication that succeeds or fails, a `AuthenticationSuccessEvent` or `AbstractAuthenticationFailureEvent ` is fired, respectively.
5
5
6
6
To listen for these events, you must first publish an `AuthenticationEventPublisher`.
7
7
Spring Security's `DefaultAuthenticationEventPublisher` will probably do fine:
@@ -42,7 +42,7 @@ public class AuthenticationEvents {
42
42
}
43
43
44
44
@EventListener
45
- public void onFailure(AuthenticationFailureEvent failures) {
45
+ public void onFailure(AbstractAuthenticationFailureEvent failures) {
46
46
// ...
47
47
}
48
48
}
@@ -70,7 +70,7 @@ While similar to `AuthenticationSuccessHandler` and `AuthenticationFailureHandle
70
70
71
71
=== Adding Exception Mappings
72
72
73
- `DefaultAuthenticationEventPublisher` by default will publish an `AuthenticationFailureEvent ` for the following events:
73
+ `DefaultAuthenticationEventPublisher` by default will publish an `AbstractAuthenticationFailureEvent ` for the following events:
74
74
75
75
|============
76
76
| Exception | Event
@@ -97,7 +97,7 @@ To that end, you may want to supply additional mappings to the publisher via the
97
97
public AuthenticationEventPublisher authenticationEventPublisher
98
98
(ApplicationEventPublisher applicationEventPublisher) {
99
99
Map<Class<? extends AuthenticationException>,
100
- Class<? extends AuthenticationFailureEvent >> mapping =
100
+ Class<? extends AbstractAuthenticationFailureEvent >> mapping =
101
101
Collections.singletonMap(FooException.class, FooEvent.class);
102
102
AuthenticationEventPublisher authenticationEventPublisher =
103
103
new DefaultAuthenticationEventPublisher(applicationEventPublisher);
0 commit comments