You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
[0.4.2]
Added
Administrators and members can sign in with passkeys. Staff add them under Security → Your account and members on the account page. Both need the current password, and each passkey can be renamed or revoked. Revoking one signs out every other device by default. A passkey works passwordless, through a button or the email field's autofill, or as the second factor after a password. The first passkey creates recovery codes, which can be regenerated. With a recovery code, or a password reset followed by one, a lost passkey does not lock the account. When everything is lost, an administrator can remove a user's passkeys, authenticator app and recovery codes from Edit user. Security → Passkeys sets a per-role policy (allow, require or disallow), user verification, attestation (none, or direct with an AAGUID allow-list), and the RP ID and extra origins. Behind a reverse proxy, those follow TRUST_PROXY. Verification uses Node's built-in crypto and needs no new dependency. Challenges are single-use and expire after five minutes, and a backwards signature counter is refused. Every step is rate limited and recorded in the audit log, and Security Center counts passkeys as administrator MFA. Migration 0056_webauthn adds the credential and challenge tables. (#105)
A plugin can back the object cache with a shared store.ctx.cache.registerStore (new cache:store permission, SDK 0.1.9) offers a store that Admin → Tools lists as a cache driver (CACHE_DRIVER=plugin:<pluginId>.<storeId>), so several application processes share cache entries and invalidations. It is honoured only from the main site and is built only when selected. Until it is ready, and during an outage, the cache is bypassed rather than failing requests: a failed read is a miss, a failed write is skipped, and after a lost invalidation the cache stays bypassed until the store is cleared. Tools and Site Health show the store's status. (#18)
Adding a site to an isolated workspace can reuse an existing administrator. Admin → Platform → Add a site offers the administrators of the workspace's sites, including sites on a separate database. The account is copied onto the new site with its password, so it is not typed in again. After that the accounts are separate. The management API takes adminFrom: { siteId, userId } in place of admin; plugins cannot copy accounts.
Owners who forgot their site address can have it emailed.POST /api/signup/find-sites with { email } mails the address the sites in every workspace it owns. Each site is listed with its address (its primary domain, custom or not) and its admin sign-in address under that site's own admin path. The installation's address is not in the email. The answer is always the same 202 and never contains sites, so it does not reveal whether an address has an account. It is limited to three requests per address per hour and five per day, and only answers on the main site. The new "Your sites" email template (core.owned-sites) is listed only on the main site.
Fixed
Saving Tools → Performance suite no longer leaves the site down when Node was started with flags. The restart started the server again without Node's own flags, such as a TypeScript loader, --env-file, or a heap size, so the new process could crash at once or run without its settings. It now keeps them, except debugger and watch flags.
A plugin page no longer shows a Settings button that leads to an empty page. The admin menu now says whether a plugin's Settings page has a settings form or sub-pages, and the plugin page header only links to it when it does.
Changed
The recommended Permissions-Policy allows passkeys on the site itself. It now sends publickey-credentials-get=(self) instead of (). A saved policy that still has the old shipped value is upgraded when read. An edited one is left as it is. Recovery codes now back up passkeys as well as the authenticator app, so turning off the authenticator keeps them while the account still has a passkey. (#105)
The unimplemented redis cache driver and CACHE_REDIS_URL are gone from core. An unknown CACHE_DRIVER now falls back to filesystem instead of failing at startup, and Tools no longer rewrites CACHE_REDIS_URL. (#18)