LegacyAuthServiceDetector
final class \
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.
Services that are not available are ignored, as the legacy chain never runs them. The native pipeline authenticators step aside in that case, so existing extensions and configurations keep working unchanged.
Internal
not part of TYPO3 Core API, only exists for the migration period towards native pipeline authenticators
Table of Contents
Methods
- requiresLegacyServiceChain() : bool
Methods
requiresLegacyServiceChain()
public
requiresLegacyServiceChain() : bool