I’m using<\/p>\n
SpringSecurity<\/a>\u00a0with\u00a0KerberosServiceAuthenticationProvider<\/a>\u00a0which is\u00a0Kerberos<\/a>\u00a0security extension<\/a>. You can read how to use it on\u00a0extension author’s blog<\/a>. But you cannot use handler on\u00a0form-login<\/a>\u00a0to catch authorization result. It’s because of inner construction of authorization filter chain calls. Maybe it can be considered a bug? The workaround is to implement\u00a0ApplicationListener<\/a><AuthenticationSuccessEvent<\/a>> and ApplicationListener<AbstractAuthenticationFailureEvent<\/a>> to catch proper events.<\/p>\n import org.springframework.context.ApplicationListener; import org.springframework.security.authentication.event.AuthenticationSuccessEvent; public class UserSuccessfulLoginLogger implements ApplicationListener{ @Override public void onApplicationEvent(AuthenticationSuccessEvent event) { \/\/do something here } }<\/p>\n import org.springframework.context.ApplicationListener; import org.springframework.security.authentication.event.AbstractAuthenticationFailureEvent; public class UserFailedLoginLogger implements ApplicationListener{ @Override public void onApplicationEvent(AbstractAuthenticationFailureEvent event) { \/\/do something here } } Then you init beans in Spring configuration<\/p>\n A drawback is that one cannot have access to request and response as could have when using authentication-success-handler-ref and authentication-failure-handler-ref. But in my case I didn’t need that.<\/p>\npackage pl.touk.app.fe.server.security;<\/pre>\n
package pl.touk.app.fe.server.security;<\/pre>\n