Merge conflict Gerrit cannot merge this change. It needs a rebase onto main.
94552[WIP][FEATURE] Passwordless passkey login for the backend
Commit message
Test this change
Run a command in your clone of the TYPO3 Core. Then try what the change does and vote on Verified in Gerrit. How to review a patch
- Check out patch set 3
-
git fetch https://review.typo3.org/Packages/TYPO3.CMS refs/changes/52/94552/3 && git checkout FETCH_HEAD - Cherry-pick onto main
-
git fetch https://review.typo3.org/Packages/TYPO3.CMS refs/changes/52/94552/3 && git cherry-pick FETCH_HEAD
Review
-
Code review CR 0 Needs a vote
-
Verified V -1 Blocked
- core-ci -1 CI
Relation chain 2
-
94552 [WIP][FEATURE] Passwordless passkey login for the backend This change
- main 97756[TASK] Share session resolution of native authenticators
Issues 1
Files 60
- Build/Sources/TypeScript/backend/passkey/passkey-autofill.tsnew+88 −0
- Build/Sources/TypeScript/backend/passkey/passkey-enrollment-prompt.tsnew+70 −0
- Build/Sources/TypeScript/backend/passkey/passkey-login.tsnew+73 −0
- Build/Sources/TypeScript/backend/passkey/passkey-manager.tsnew+227 −0
- Build/Sources/TypeScript/backend/passkey/passkey-register-ceremony.tsnew+130 −0
- Build/Sources/TypeScript/backend/passkey/passkey-webauthn.tsnew+88 −0
- typo3/sysext/backend/Classes/Controller/BackendController.php+7 −0
- typo3/sysext/backend/Classes/Controller/LoginController.php+5 −1
- typo3/sysext/backend/Classes/Controller/PasskeyController.php1new+214 −0
- typo3/sysext/backend/Classes/Form/Element/PasskeyManagementElement.phpnew+58 −0
- typo3/sysext/backend/Classes/Form/NodeFactory.php+1 −0
- typo3/sysext/backend/Classes/LoginProvider/PasskeyLoginProvider.phpnew+56 −0
- typo3/sysext/backend/Classes/Security/Passkey/PasskeyConditionalLoginListener.phpnew+65 −0
- typo3/sysext/backend/Classes/Security/Passkey/PasskeyEnrollmentPromptListener.phpnew+69 −0
- typo3/sysext/backend/Classes/Security/Passkey/PasskeyVoter.phpnew+99 −0
- typo3/sysext/backend/Classes/Security/BackendCredentialLogin.phpnew+176 −0
- typo3/sysext/backend/Classes/Security/BackendLoginAttempt.phpnew+47 −0
- typo3/sysext/backend/Classes/Security/PasskeyAuthenticator.phpnew+115 −0
- typo3/sysext/backend/Classes/Security/PasswordAuthenticator.php+19 −114
- typo3/sysext/backend/Configuration/Backend/AjaxRoutes.php+33 −0
Show 40 more files
- typo3/sysext/backend/Configuration/TCA/Overrides/be_users.php+15 −0
- typo3/sysext/backend/Resources/Private/Language/locallang_passkey.xlfnew+182 −0
- typo3/sysext/backend/Resources/Private/Layouts/Login.fluid.html+4 −4
- typo3/sysext/backend/Resources/Private/Templates/Email/Security/PasskeyEnrolledNotification.fluid.htmlnew+7 −0
- typo3/sysext/backend/Resources/Private/Templates/Email/Security/PasskeyEnrolledNotification.fluid.txtnew+8 −0
- typo3/sysext/backend/Resources/Private/Templates/Login/PasskeyLoginForm.fluid.htmlnew+43 −0
- typo3/sysext/backend/Resources/Public/JavaScript/passkey/passkey-autofill.jsnew+13 −0
- typo3/sysext/backend/Resources/Public/JavaScript/passkey/passkey-enrollment-prompt.jsnew+13 −0
- typo3/sysext/backend/Resources/Public/JavaScript/passkey/passkey-login.jsnew+13 −0
- typo3/sysext/backend/Resources/Public/JavaScript/passkey/passkey-manager.jsnew+13 −0
- typo3/sysext/backend/Resources/Public/JavaScript/passkey/passkey-register-ceremony.jsnew+13 −0
- typo3/sysext/backend/Resources/Public/JavaScript/passkey/passkey-webauthn.jsnew+13 −0
- typo3/sysext/backend/Tests/Functional/Middleware/Fixtures/SoftwarePasskey.phpnew+88 −0
- typo3/sysext/backend/Tests/Functional/Middleware/BackendUserAuthenticatorTest.php+225 −0
- typo3/sysext/backend/Tests/Unit/Security/Passkey/PasskeyVoterTest.phpnew+122 −0
- typo3/sysext/backend/ext_localconf.php+8 −0
- typo3/sysext/core/Classes/Authentication/Passkey/AuthenticatorMetadata.phpnew+45 −0
- typo3/sysext/core/Classes/Authentication/Passkey/Passkey.phpnew+64 −0
- typo3/sysext/core/Classes/Authentication/Passkey/PasskeyAssertion.phpnew+55 −0
- typo3/sysext/core/Classes/Authentication/Passkey/PasskeyAssertionService.php2new+192 −0
- typo3/sysext/core/Classes/Authentication/Passkey/PasskeyAuthenticationOptions.phpnew+32 −0
- typo3/sysext/core/Classes/Authentication/Passkey/PasskeyChallengeService.phpnew+94 −0
- typo3/sysext/core/Classes/Authentication/Passkey/PasskeyDataHandlerCleanup.phpnew+46 −0
- typo3/sysext/core/Classes/Authentication/Passkey/PasskeyRegistrationService.php1new+143 −0
- typo3/sysext/core/Classes/Authentication/Passkey/PasskeyRepository.phpnew+201 −0
- typo3/sysext/core/Classes/Authentication/Passkey/WebAuthnHelperTrait.phpnew+57 −0
- typo3/sysext/core/Classes/Authentication/Pipeline/LegacyUserPrincipalFactory.php+28 −2
- typo3/sysext/core/Classes/Authentication/AbstractUserAuthentication.php+2 −2
- typo3/sysext/core/Classes/Authentication/Principal.php+19 −0
- typo3/sysext/core/Classes/Security/LoginRequestTokenVerifier.phpnew+65 −0
- typo3/sysext/core/Classes/Security/PasswordCredentialVerifier.php+4 −33
- typo3/sysext/core/Configuration/TCA/be_users.php+12 −1
- typo3/sysext/core/Tests/Functional/Security/LoginRequestTokenVerifierTest.phpnew+93 −0
- typo3/sysext/core/Tests/Functional/Security/PasswordCredentialVerifierTest.php+0 −66
- typo3/sysext/core/composer.json+2 −1
- typo3/sysext/core/ext_localconf.php+13 −0
- typo3/sysext/core/ext_tables.sql2+23 −1
- typo3/sysext/frontend/Classes/Security/FrontendPasswordAuthenticator.php+4 −2
- composer.json+2 −1
- composer.lock+727 −86
Review log 1012
-
Benjamin Kott uploaded patch set 1 06/23/26, 09:39
-
Benjamin Kott commented on patch set 1 06/23/26, 09:41
EARLY incomplete poc, still needs discussions first before making it public and also requires some prework -
Benni Mack commented on patch set 1 07/01/26, 11:47
just to weigh-in here: Olly H. and me discussed this feature a while ago, the main issue is that passkey is connected to the domain (= web domain). If you enable this in a dev environment, you might not be able to log in to the backend on prod? Haven't tried your solution yet, but this needs to be considered and documented. -
Benjamin Franzke commented on patch set 1 07/01/26, 13:00
Reply
ack, had/have the same documentation challenge in EXT:mfa_webauthn, see: https://github.com/bnf/mfa_webauthn#using-webauthn-provider-in-production-and-staging-environments -
Benjamin Kott wrote 08/09/26, 06:35
Unset private -
Benjamin Kott marked it work in progress 08/09/26, 06:35
-
Benni Mack uploaded patch set 2 11/18/26, 21:41
-
Benni Mack uploaded patch set 3 11/18/26, 22:18
-
core-ci voted on patch set 3 V -1 11/18/26, 22:33 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/114939
-
core-ci voted on patch set 2 V -1 11/18/26, 22:42 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/114934
-
Sebastian Mendel commented on patch set 3 11/18/26, 22:46
Points beyond CI and the open list in the commit message: 1. be_users_passkeys.credential_id is varchar(700) and holds the base64url form. WebAuthn L3 allows credential IDs up to 1023 bytes (1364 chars base64url), so credentials with IDs above 525 bytes cannot be stored (error on MySQL strict mode / Postgres). Also, credential_id and passkey_user_handle hold case-sensitive base64url in varchar columns, which compare case-insensitively under utf8mb4_unicode_ci, the collation the installer sets for MySQL/MariaDB. Storing the raw bytes as varbinary (supported by the core schema parser) would fix both. 2. The assertion uses userVerification "preferred". A passkey without UV then logs in passwordless with possession as the only factor; the data set "device-bound passkey without user verification" in BackendUserAuthenticatorTest shows such a login succeeding. Could the assertion require UV, or make it configurable with "required" as default? Registration already requires UV; the code comment mentions authenticators setting the flag inconsistently on assertion, which would be good to back with a concrete case. 3. Enrollment, removal and admin revocation of a passkey write no sys_log entry, and removal is a hard delete. For an authentication credential an audit trail (who added/removed which passkey, admin vs. self) seems needed; a soft revoke (revoked_at/revoked_by) would keep it queryable. 4. There are no PSR-14 events for passkey enrollment and removal (login itself goes through the generic AfterUserLoggedInEvent / LoginAttemptFailedEvent). Extensions that need enforcement or auditing around credential changes have no hook point. Nits: the docblocks of PasskeyAssertionService and PasskeyRepository still mention resolving via makeInstance() from a non-DI service; no such caller exists. A test for "credential of user A submitted with the user handle of user B" would cover the unknown-passkey path. -
Sebastian Mendel commented on patch set 3 11/18/26, 23:03
Unresolved
My earlier review was posted as a plain change message, which cannot be replied to or resolved. The same points are now inline comments. One more: a test for "credential of user A submitted with the user handle of user B" would cover the unknown-passkey path.PasskeyController.php:155UnresolvedEnrollment, removal and admin revocation write no sys_log entry, and this is a hard delete. For an authentication credential an audit trail (who added/removed which passkey, admin vs. self) seems needed; a soft revoke (revoked_at/revoked_by) would keep it queryable.PasskeyAssertionService.php:39UnresolvedNit: no makeInstance() caller exists for this class (same docblock in PasskeyRepository); the docblock and possibly #[Autoconfigure(public: true)] look stale.PasskeyAssertionService.php:153UnresolveduserVerification "preferred" (here and in line 71): a passkey without UV logs in passwordless with possession as the only factor; the data set "device-bound passkey without user verification" in BackendUserAuthenticatorTest shows such a login succeeding. Could the assertion require UV, or make it configurable with "required" as default? Registration already requires UV; the comment about authenticators setting the flag inconsistently would be good to back with a concrete case.PasskeyRegistrationService.php:132UnresolvedThere are no PSR-14 events for passkey enrollment and removal (login itself goes through the generic AfterUserLoggedInEvent / LoginAttemptFailedEvent). Extensions that need enforcement or auditing around credential changes have no hook point.ext_tables.sql:23Unresolvedpasskey_user_handle and credential_id hold case-sensitive base64url in varchar columns. Under utf8mb4_unicode_ci, the collation the installer sets for MySQL/MariaDB, lookups compare case-insensitively. Raw bytes in varbinary (e.g. varbinary(64) here) would avoid that.ext_tables.sql:33Unresolvedcredential_id is varchar(700) and holds the base64url form. WebAuthn L3 allows credential IDs up to 1023 bytes (1364 chars base64url), so credentials with IDs above 525 bytes cannot be stored (error on MySQL strict mode / Postgres). Storing the raw bytes as varbinary(1023) would fit every valid ID; the core schema parser supports varbinary.