67896[WIP][BUGFIX] Fix access to public backend routes of extensions
Commit message
Review
-
Code review CR 0
-
Verified V -1
- core-ci -1 CI
Files 1
Review log 58
-
Benjamin Franzke uploaded patch set 1 02/12/21, 08:21
-
TYPO3com voted on patch set 1 V +1 02/12/21, 08:29 Completed build in 08m 19s on Fri, 12 Feb, 08:29 AM Test Summary: 32611 passed Find logs and detail information at https://bamboo.typo3.com/browse/CORE-GTC-9497
-
core-ci voted on patch set 1 V +1 02/12/21, 08:32 Core CI is happy: https://core.b13.com/typo3-core/typo3.cms/-/pipelines/683
-
Benni Mack wrote 11/29/21, 10:03
Change destination moved from master to main -
Benni Mack updated the commit message in patch set 2 11/29/21, 13:14
-
core-ci voted on patch set 2 V -1 11/29/21, 13:30 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/19993
-
Benjamin Franzke commented on patch set 2 02/20/22, 06:59
Unresolved
double-meaning of "public": In Routes-Config "public" means => no token required to call the route In the middleware "public" means" => no backend login required to call the route /ajax/login/refresh is special, because it requires a route-token but is still allowed for non-logged-in users Solutions? Dont know… * Add a access=protected option? (requires token, but no login) * Add a custom tokne for the refresh-url? * Do we actually need to allow login/refresh in BackendUserAuthenticator – after all a authenticated session is required to refresh the session. or is a timeout sesson refreshable(?) -
Benjamin Franzke abandoned the change 01/30/26, 15:04