When running a login or logout flow, the GetUserFilter triggers a first
WebSession.getUser() causing the loading of current user as anonymous
(or IdentifiedUser).
When another filter tries to retrieve the current user from a
Provider<CurrentUser> would then get anonymous even if the user is
actually logged in or just logged out.
Fix this situation by forcing the re-creation of current user after a
session login or logout.
Change-Id: Ia33faf2cdd406e910339f3aebbc054a8f1f00e7a
33237003a6