Remember me login fired multiple times

Summary

We're handling the InteractiveAuthenticationSuccessEvent to determine when a user logged in. However, this event is getting fired multiple times, causing unexpected behavior in our application.
It seems when accessing a page requiring full authentication, the security context is cleared in the ExceptionTranslationFilter, causing a partially authenticated user to be in effect logged out. The user will then be redirected to the login page, where remember me login kicks in again (the cookie is still present).
Seems to be a side effect of the fix for this issue.

Actual Behavior

1. User accesses any page. Remember-me kicks in and user is logged in automatically. InteractiveAuthenticationSuccessEvent is published.
2. User accesses page requiring full authentication and is redirected to login page*. Remember-me kicks in again and InteractiveAuthenticationSuccessEvent is published.
   *Login page itself is not the issue, since remember-me will kick in regardless of which page we redirect to.

Expected Behavior

• InteractiveAuthenticationSuccessEvent should be fired only once, in step 1.
• Logout/login should not be repeated in circles behind the scenes.

Configuration

A mix of authenticated and fullyAuthenticated urls.
Persistent token based remember-me enabled:

    .and().rememberMe()
    	.key(REMEMBER_ME_CRYPTO_KEY)
    	.alwaysRemember(true)
    	.tokenValiditySeconds(REMEMBER_ME_TOKEN_VALIDITY)
    	.userDetailsService(userDetailsService)
    	.rememberMeServices(rememberMeServices)
    	.tokenRepository(rememberMeTokenRepository)
        .useSecureCookie(true)

The overall configuration is too customized to describe here. If others haven't experienced/can't reproduce this issue, I will try to provide a sample. Just didn't have time at the moment.

Version

5.0.7.RELEASE

Start with ExceptionTranslationFilter.java at the linked security-context clearing lines, then trace the remember-me authentication flow using the mixed authenticated and fullyAuthenticated URL configuration described here. Reproduce the redirect scenario and verify that InteractiveAuthenticationSuccessEvent is published once without repeated logout/login behavior.