Enforcement
The enforcement system controls how strongly passkeys are required for frontend users. Enforcement can be set at the site level and overridden per frontend user group.
Enforcement levels
Four levels are available:
- Off
- Passkeys are completely optional. No prompts, banners, or interstitials. Users can log in with a password as normal.
- Encourage
- Users without a passkey see a dismissible banner after login suggesting they enroll one. No access is blocked. The banner can be dismissed and will not re-appear for the session.
- Required
- Users without a passkey see an enrollment interstitial after login. They can skip the interstitial during the grace period (configurable, default 14 days). After the grace period expires, they must enroll to continue.
- Enforced
- Users without a passkey cannot bypass the enrollment interstitial. Grace period skipping is disabled. This level is suitable for high-security sites.
Enforcement resolution
The effective enforcement level for a user is determined by:
- Site configuration -- The site-level
enforcementsetting (see Site Configuration).Level - User group overrides -- Each frontend user group can have an enforcement level. The strictest level across all groups the user belongs to wins.
- Grace period -- The shortest grace period across applicable groups wins.
The Enforcement PSR-14 event allows listeners to
further override the resolved level (see PSR-14 Events).
Configuring per-group enforcement
In the TYPO3 backend:
- Go to Web > List and open the
fe_record.groups - The TCA record shows a Passkey Enforcement section.
- Set the enforcement level and grace period for the group.
Or use the backend module:
- Go to Admin Tools > Passkey Management FE.
- In the Enforcement tab, select a site.
- Adjust enforcement levels per group.
Interstitial behaviour
When a user triggers the enrollment interstitial (level required
or enforced):
- The full-page interstitial is shown.
- It explains why a passkey is required.
- It shows the enrollment form (links to the enrollment page).
- For
requiredlevel: a Skip for now button is shown with the remaining grace period. - For
enforcedlevel: no skip button. - API endpoints, AJAX requests, and the login/logout pages are exempted from the interstitial.
Grace period tracking
Grace periods are tracked per user in the fe_ table via the
passkey_ column: the unix timestamp of the user's
first frontend request under required enforcement without a passkey,
whatever page it is for. The enrollment interstitial writes it, so it is
only written while post-login enrollment is enabled (the default). The start is
written once. Changing the enforcement level or the grace period days later
does not refresh it, and an expired grace period stays expired; an
administrator starts a new one with Reset grace period (see
User Management).
The grace period ends grace × 24 hours after the start. The
banner and the enrollment page show the remaining days as started 24-hour
periods, so a 14-day grace period shows 14 days at its start and 1 day
during its last 24 hours.
Per-group grace period days are stored in fe_.
The shortest grace period across all applicable groups wins.