Issue Task Resolved

#110863Improved configuration of public backend routes

Benni Mack 09/30/26, 15:12 updated 10/02/26, 08:40

Description

Which backend routes may be reached without a login is currently defined in two places that have drifted apart:

- BackendUserAuthenticator::$publicRoutes is a hardcoded list of 15 route paths. It decides whether a backend user is required.
- The route option ‘access’ => ‘public’ decides whether a request token is created and validated.

The two are problematic today:

- ajax_login_refresh is in the path list but has no access option. It needs no user, yet it still gets a token check that DisabledFormProtection passes for any non-empty token.
- state-tracker and language_domain have access => ‘public’ but are not in the list. They only use public to skip the token, and still require a login.
- Extensions cannot add to the list, and it matches on paths, not route identifiers.

Reviews 1

History 13

  1. Benni Mack commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-10-02T08:40:10+00:00" > 10/02/26, 08:40 </span>

    Applied in changeset commit:d5d9dc01a46df7734b4973b4295c5bfb3f561274.