Issue Feature Resolved

#111399Add native backend authenticators

Benni Mack 11/10/26, 18:12 updated 11/17/26, 14:30

Description

Backend logins are still processed by the legacy authentication service chain (T3_SERVICES), although the authentication pipeline (#110448) can run authenticators of its own per realm.

Proposal

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

  • PasswordAuthenticator processes submitted credentials, bound to the backend login routes, including the request token check, rate limiting, timing mitigation for unknown users, password rehashing, session fixation protection, logging and the existing PSR-14 events.
  • SessionAuthenticator resolves an existing user session, handles logout requests and expired sessions, and starts the multi-factor authentication challenge when required.
  • Users are looked up through one identity provider, the single place querying be_users records including the enable columns.

The native authenticators only engage when no third-party authentication service is registered. As soon as an extension adds an authentication service, the legacy service chain processes the request exactly as before.

Behavior change of the native path: credentials posted to backend URLs outside the login routes are ignored.

Reviews 1

History 27

  1. Gerrit Code Review pushed patch set 20 for main to change 95287 status New Under Review <span data-processor="relativetime" data-value="2026-11-10T20:26:11+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-17T14:30:15+00:00" > 11/17/26, 14:30 </span>

    Applied in changeset commit:2ebdb1d66eb51bd81a7c5232cdbd1b53622de2e8.