Pipeline

namespace TYPO3\CMS\Core\Authentication\Pipeline

Table of Contents

Interfaces

AuthenticationResult
Union type of the possible outcomes of an authentication attempt:
AuthenticatorInterface
A single, composable step in the authentication pipeline of a realm.

Classes

Authenticated
Successful authentication outcome carrying the established Principal.
AuthenticatorManager
Resolves a request to an authentication outcome by asking the authenticators registered for the realm in order of their priority.
Challenge
Authentication outcome demanding an interactive step from the caller, carrying the PSR-7 response that initiates it. A redirect to an identity provider or multi-factor view, a WebAuthn ceremony, or a plain 401.
Failure
Explicitly failed authentication attempt. Loggable and countable towards rate limits, with an optional message safe to show to users.
LegacyAuthServiceDetector
Detects whether authentication must be routed through the legacy authentication service chain: either because the available "auth" services differ from the core authentication service (an extension registered an additional service, or the core service is disabled), or because the chain behavior is modified through service configuration, the core service class is replaced (service className or XCLASS) or a "postUserLookUp" hook is registered, which only the legacy chain calls.
LegacyUserPrincipalFactory
Builds a Principal snapshot from a legacy user authentication object, for the authenticators as well as for authorization decisions on behalf of any backend user: isGrantedForUser(new PrincipalUser($principal), ...).
LoginRateLimiterGuard
Applies the login rate limit for active login attempts.
NotApplicable
Authentication outcome stating that the authenticator is not responsible for the given request, for example as it carries no credentials for it.
Realm
Describes a security zone authentication is performed for. The TYPO3 backend, the frontend of a site, or a custom realm such as a token based API.
On this page