Issue Task Under Review

#111477Share session resolution of native authenticators and password check with legacy chain

Benni Mack 11/17/26, 16:13 updated 11/18/26, 22:18

Description

The native session and password authenticators of backend and frontend each resolve the user session of a request on their own: reading the session cookie, logging off an expired session, looking up the user of the session and refreshing the session timestamp. The legacy user authentication does the same in fetchValidUserFromSessionOrDestroySession().

These steps should live in one internal UserSessionResolver, used by all four native authenticators, which looks users up via the LocalIdentityProvider.

In addition, the legacy authentication chain (AbstractUserAuthentication::checkAuthentication() and AuthenticationService::authUser()/mimicAuthUser()) still carries its own copy of the request token check and the password verification including rehashing. It should use the PasswordCredentialVerifier introduced with #111470, so native and legacy authentication cannot drift apart.

Reviews 1

History 02