Issue Feature Resolved

#111400Add native frontend authenticators

Benni Mack 11/10/26, 18:13 updated 11/17/26, 15:15

Description

Frontend logins are still processed by the legacy authentication service chain (T3_SERVICES), which inspects every request for credentials. The authentication pipeline (#110448) can run authenticators of its own per realm, as done for the backend in #111399.

Proposal

Provide frontend session resolution and password evaluation as native pipeline authenticators:

  • FrontendPasswordAuthenticator processes credentials submitted with logintype=login on any page URL, so that login forms on arbitrary pages (such as the felogin plugin) keep working, now with an explicit trigger instead of looking for credentials on every request. The storage page restriction passed by the felogin form via the signed request token, permanent login (“stay logged in”) and the existing events are preserved.
  • FrontendSessionAuthenticator resolves an existing user session and handles logout requests. It always resolves the group data, so that group simulation keeps working.

As in the backend, the native authenticators only engage when no third-party authentication service is registered. Otherwise the legacy service chain processes the request unchanged.

Reviews 1

History 28

  1. Gerrit Code Review pushed patch set 20 for main to change 95288 status New Under Review <span data-processor="relativetime" data-value="2026-11-10T20:26:12+00:00" > 11/10/26, 20:26 </span>

  2. Benni Mack commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-11-17T15:15:13+00:00" > 11/17/26, 15:15 </span>

    Applied in changeset commit:eaa8f182db8d350fdbf6404fc3a8981af9fb271d.