Multi-Site 

TYPO3 multi-site installations require each site to have its own passkey configuration because WebAuthn credentials are bound to a specific domain (Relying Party ID).

How site-aware RP ID works 

When a passkey authentication or enrollment request arrives, the extension resolves the current TYPO3 site from the request and reads the nr_passkeys_fe.rpId value from the site's config.yaml.

If no per-site RP ID is configured, the extension falls back to the global extension setting (auto-detected from HTTP_HOST).

This means:

  • Credentials registered on site-a.example cannot be used on site-b.example.
  • Each site maintains its own independent credential store (filtered by site RP ID).
  • Users who access multiple sites must enroll a passkey separately on each site.

Configuration example 

For a TYPO3 installation with two separate domains:

config/sites/company-intranet/config.yaml
base: 'https://intranet.example.com/'
settings:
  nr_passkeys_fe:
    rpId: 'intranet.example.com'
    origin: 'https://intranet.example.com'
    enforcementLevel: 'enforced'
    enrollmentPageUrl: '/passkey-setup'
Copied!
config/sites/public-shop/config.yaml
base: 'https://shop.example.com/'
settings:
  nr_passkeys_fe:
    rpId: 'shop.example.com'
    origin: 'https://shop.example.com'
    enforcementLevel: 'encourage'
    enrollmentPageUrl: '/passkey-setup'
Copied!

Shared RP ID across subdomains 

WebAuthn allows trusted subdomains to share a parent RP ID. TYPO3 still looks up each credential by the current site's identifier. Users who sign in to two TYPO3 sites register a passkey on each site.

For example, these sites use the same RP ID and distinct origins:

# site-a/config.yaml
settings:
  nr_passkeys_fe:
    rpId: 'example.com'
    origin: 'https://app.example.com'

# site-b/config.yaml
settings:
  nr_passkeys_fe:
    rpId: 'example.com'
    origin: 'https://api.example.com'
Copied!

Database isolation 

Credentials are stored with a site_identifier column in tx_nrpasskeysfe_credential. The credential lookup in the auth service always filters by the current site's identifier. There is no cross-site credential leakage.

Migration from single-site to multi-site 

If you initially deployed without per-site RP ID configuration (using auto-detected RP ID) and later add multiple sites:

  1. The auto-detected RP ID was HTTP_HOST from the original request.
  2. Existing credentials have a site_identifier matching the original site.
  3. When adding a new site with a different domain, users must re-enroll (their existing credentials won't match the new RP ID).

Plan migrations carefully and communicate re-enrollment to users in advance.

Frontend account folders 

By default, a frontend account's current storage page must belong to the request's TYPO3 site. For shared user folders configure the comma-separated site setting nr_passkeys_fe.userStoragePids with the permitted page IDs. An omitted value, an empty string, or an empty list uses the site's own page tree. To share a folder, list its page ID on each participating site. Credential use also requires its original registration site. Existing credentials without a stored folder are checked against their owner's current folder and the recorded site on each login.

On an enforced site, an enrolled account needs a session established on that site with a passkey or a permitted recovery code. Signing in with a password allows initial enrollment. After registering the first passkey, sign in with it to continue. Existing sessions without a site-bound proof require a fresh login when the site enforces passkeys.

Recovery codes and rollout 

Apply the updated database schema and deploy the backend extension update before enabling the frontend workers. New recovery sets belong to one site. The extension assigns old unscoped codes only to the site containing the user's storage folder. A shared folder outside a configured site has no automatic assignment. Before cutover, establish a working passkey or supervised account recovery for these accounts and reissue their codes. Generate a separate set on each site where recovery is enabled.

All sites share a recovery verification budget in addition to the IP and account limits. Monitor HTTP 429 responses and size recovery capacity and the database limits for the deployment.