---
title: "Breaking: #102605 - TSFE->fe_user removed"
manual: "TYPO3 Core Changelog"
version: "main"
permalink: "https://docs.typo3.org/permalink/changelog:breaking-102605-1701772495"
source: "Changelog/13.0/Breaking-102605-TSFE-fe_userRemoved.rst"
typo3-version: "13.0"
typo3-major: 13
type: "breaking"
issue: 102605
forge: "https://forge.typo3.org/issues/102605"
tags: ["Frontend", "PHP-API", "FullyScanned", "ext:frontend"]
rendered: "2026-10-03T08:19:36+00:00"
---

# Breaking: #102605 - TSFE->fe_user removed {#breaking-102605-1701772495}

See [forge#102605](https://forge.typo3.org/issues/102605)

## Description {#description}

Frontend-related property `TypoScriptFrontendController->fe_user` has been removed.

When looking at the TYPO3 frontend rendering chain, class `TypoScriptFrontendController`
is by far the biggest technical debt: It mixes a lot of concerns and carries tons of state
and functionality that should be modeled differently, which leads to easier to understand
and more flexible code. The class is shrinking since various major versions already and will
ultimately dissolve entirely at some point. Changes in this area are becoming more aggressive
with TYPO3 v13. Any code using the class will need adaptions at some point, single patches
will continue to communicate alternatives.

In case of the `fe_user` property, two alternatives exist: The frontend user
can be retrieved from the PSR-7 request attribute `frontend.user`, and basic frontend user
information is available using the `Context` aspect `frontend.user`.

Note accessing TypoScript `TSFE:fe_user` details continues to work for now, using
for example `lib.foo.data = TSFE:fe_user|user|username` to retrieve the username of a
logged in user is still ok.

## Impact {#impact}

Using `TypoScriptFrontendController->fe_user` (or
`$GLOBALS['TSFE']->fe_user`) will raise a PHP fatal error.

## Affected installations {#affected-installations}

Instances with extensions dealing with frontend user details may be affected, typically
custom login extensions or extensions consuming detail data of logged in users.

## Migration {#migration}

There are two possible migrations.

First, a limited information list of frontend user details can be retrieved using the `Context`
aspect `frontend.user` in frontend calls. See class `\TYPO3\CMS\Core\Context\UserAspect` for a
full list. The current context can retrieved using dependency injection. Example:

```php
use TYPO3\CMS\Core\Context\Context;

final class MyExtensionController {
    public function __construct(
        private readonly Context $context,
    ) {}

    public function myAction() {
        $frontendUserUsername = $this->context->getPropertyFromAspect('frontend.user', 'username', ''));
    }
}
```

Additionally, the full `\TYPO3\CMS\Frontend\Authentication\FrontendUserAuthentication` object is
available as request attribute `frontend.user` in the frontend. Note some details of that object
are marked `@internal`, using the context aspect is thus the preferred way. Example of an extension
using Extbase's `ActionController`:

```php
final class MyExtensionController extends ActionController {
    public function myAction() {
        // Note the 'user' property is marked @internal.
        $frontendUserUsername = $this->request->getAttribute('frontend.user')->user['username'];
    }
}
```