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:
@@ -27,7 +27,7 @@ public class AuthenticationEvents {
27
27
}
28
28
29
29
@EventListener
30
- public void onFailure(AuthenticationFailureEvent failures) {
30
+ public void onFailure(AbstractAuthenticationFailureEvent failures) {
31
31
// ...
32
32
}
33
33
}
@@ -37,7 +37,7 @@ While similar to `AuthenticationSuccessHandler` and `AuthenticationFailureHandle
37
37
38
38
=== Adding Exception Mappings
39
39
40
- `DefaultAuthenticationEventPublisher` by default will publish an `AuthenticationFailureEvent ` for the following events:
40
+ `DefaultAuthenticationEventPublisher` by default will publish an `AbstractAuthenticationFailureEvent ` for the following events:
41
41
42
42
|============
43
43
| Exception | Event
@@ -62,7 +62,7 @@ To that end, you may want to supply additional mappings to the publisher via the
62
62
public AuthenticationEventPublisher authenticationEventPublisher
63
63
(ApplicationEventPublisher applicationEventPublisher) {
64
64
Map<Class<? extends AuthenticationException>,
65
- Class<? extends AuthenticationFailureEvent >> mapping =
65
+ Class<? extends AbstractAuthenticationFailureEvent >> mapping =
66
66
Collections.singletonMap(FooException.class, FooEvent.class);
67
67
AuthenticationEventPublisher authenticationEventPublisher =
68
68
new DefaultAuthenticationEventPublisher(applicationEventPublisher);
0 commit comments