@clerk/localizations

Minor Changes

• Support passkeys as a second factor during sign-in and session reverification.

  When a user has a passkey, the prebuilt <SignIn/> and <UserVerification/>
  components preselect it as the second factor, as they already do for the first
  factor. Other methods stay available under "Use another method".

  To use it, your instance must allow passkeys to satisfy the second factor. This
  is on by default for instances created after 2026-07-08, and can be turned on
  in the Dashboard for older ones. Web apps also need to opt in to the passkey
  second factor update in the Dashboard.

  If you build a custom flow, supportedSecondFactors can now include passkey.
  Call signIn.authenticateWithPasskey() to complete it.

  Passkeys are no longer preselected, for either factor, where the SDK reports
  that WebAuthn is unavailable (for example, Electron apps without passkey
  support enabled).

Patch Changes

• Add a module field pointing to the ESM build, so bundlers that don't read exports (such as Parcel in Plasmo-based Chrome extensions) can tree-shake unused locales.

Minor Changes

• Add a role mapping step to the self-serve Directory Sync setup in <OrganizationProfile />. Organization admins can now assign an organization role to each directory group their identity provider pushes, set which group wins when a member belongs to several, and turn role syncing on or off. Members in no mapped group keep the organization's default role. The step is read-only for members without the org:sys_memberships:manage permission and while the organization's role set is being migrated.

Minor Changes

• The self-serve SSO configuration (<OrganizationProfile /> enterprise connection page and the ConfigureSSO SAML steps) now shows every IdP signing certificate a SAML connection trusts, with its expiry, and lets an admin add certificates from a file (a PEM bundle adds several) or remove one, so an IdP key rotation no longer needs a replacement timed with the IdP. Saving sends the whole list and only when it changed. The list holds at most five certificates. New configureSSOCertificateList* and configureSSOCertificatePrimaryBadge appearance element descriptors cover the list, and new configureSSO.signingCertificates.* localization keys hold its strings.

Minor Changes

• Support Google Workspace directories in Directory Sync. Organization admins can upload a service account key and delegated admin email from the setup flow, start a sync on demand, and see the result of the last one. DirectorySync gains setCredentials(), sync(), getSyncStatus(), and credentialsConfigured.

• Update the SSO and Directory Sync sections of the <OrganizationProfile /> Security page to the latest designs. Both sections now show a "Configure" button until something is set up (SSO then shows "Add connection"), and SSO connection rows show the identity provider's logo and an actions menu (Edit, Continue configuration, Activate/Deactivate, Remove). These actions have been removed from the SSO connection page, and status badges are no longer color-coded. Okta logos now follow the theme's foreground color, so they stay visible in dark mode, including on the enterprise connection chooser and in <UserProfile />.

  The SSO button uses the new ssoSection.primaryButton__configure localization key; ssoSection.primaryButton__startConfiguration is deprecated and no longer used. In directorySyncSection, primaryButton__startConfiguration is renamed to primaryButton__configure and badge__unconfigured is removed.

Patch Changes

• Add a localized message for the too_many_unverified_identifications error, shown when adding an email address or phone number is blocked by pending verifications or an incomplete passkey setup.

Minor Changes

• <SignIn /> and <SignUp /> show a dedicated screen when a request is blocked, with a reference the user can quote to support.

  action_blocked errors now expose traceId, title, description, linkUrl, linkText, kind and data on meta.

Patch Changes

• Fix enterprise SSO sign-ins erroring instead of showing a verification challenge raised while handing off to the identity provider.

  If you use the prebuilt <SignIn /> component, there is nothing to do. If you have Clerk Protect enabled and call signIn.authenticateWithRedirect() or signIn.authenticateWithPopup() from a custom sign-in flow, catch a ClerkRuntimeError with code protect_check_required and show the verification challenge, to avoid a stalled sign-in.

  That error means a verification challenge has to be completed before the sign-in can redirect. It replaces the generic "not supported" error these methods threw before. When it is thrown, the sign-in is gated: signIn.protectCheck is set, or its status is needs_protect_check. For enterprise SSO, run the challenge and then call authenticateWithRedirect() again with continueSignIn: true. If the server has already prepared the redirect, the sign-in continues to the identity provider and the challenge runs when it returns, so no error is thrown.

Minor Changes

• The "Add members" card on the SSO allow list page of <OrganizationProfile /> now offers two ways to add people: by email address, or every member with a given role at once. Members whose email address is not served by one of the organization's enterprise connections are skipped. When nothing could be added the card stays open and says why, and when some were added it moves to a success step that reports how many were skipped.

  For custom flows, organization.ssoBypassAllowlist gains addUsers({ userIds }), which calls the new bulk endpoint in batches of 100 and returns the added entries together with the users that could not be added and why.

  Inputs marked to be ignored by password managers now also carry the Bitwarden, LastPass and Dashlane opt-out attributes, so those extensions stop offering to fill fields such as the allow list email address.

  The member picker that the "Add member" card shipped with in 4.18.0 is gone, and so are its localization keys under organizationProfile.securityPage.ssoBypassPage.addForm: memberLabel, memberPlaceholder, changeButton and noResults. The feature was never enabled on any instance, so no application depends on them.

  New customization handles: the organizationProfileSecuritySsoBypassEmailInput, organizationProfileSecuritySsoBypassRoleWarning, organizationProfileSecuritySsoBypassFailure and organizationProfileSecuritySsoBypassBulkResult appearance elements.

• Localize icon-only social sign-in button names using socialButtonsBlockButton and exclude decorative provider icons from the accessibility tree. Add formFieldAction__showPassword and formFieldAction__hidePassword localization keys for password visibility controls, with translations for every supported locale and English fallback for older localization resources.

Patch Changes

• Show the provider logo next to each connection name on the enterprise account chooser.

Minor Changes

• Rename the SSO fallback sign-in flow to SSO bypass, matching the name the feature ships under. The sign-in resource's ssoFallbackFirstFactors is now ssoBypassFirstFactors and reads the sso_bypass_first_factors field from the API, the signIn.ssoFallback localization keys are now signIn.ssoBypass, and the ssoFallback card action element id is now ssoBypass. The flow has not been enabled on any instance, so no application is affected by the old names going away.

• Add the ability for Organization admins to manage the SSO bypass allowlist from the Security page of <OrganizationProfile />.

  For custom flows, organization.ssoBypassAllowlist exposes getUsers(), addUser({ userId }) and removeUser(userId).

Patch Changes

• Each enterprise connection listed on the organization Security page now opens its own page. It lists the connection name and domains, the service provider values to copy into the identity provider, the identity provider configuration behind an Edit form, and the connection settings as a form you save. The header carries one action, either Activate or Continue setup, and deactivating or removing the connection lives in a Danger zone section at the bottom of the page. The row menu is gone; click the row instead.

  The setup wizard's domains step now shows a checkbox per verified domain, so an admin picks which domains a connection covers. A domain another connection of the organization already authenticates is disabled and labelled with that connection's name, and an error from creating the connection is shown on the provider step instead of being dropped.

  New customization handles ship with it: the organizationProfileSecuritySsoConnectionRow and organizationProfileSecuritySsoConnectionPage appearance elements, the configureSSOVerifyDomainCardCheckbox element, the claimed badge id, the new FieldId values for the connection settings, and the ssoConnectionName, ssoConnectionDomains, ssoConnectionServiceProvider, ssoConnectionIdentityProvider, ssoConnectionSettings and ssoConnectionDangerZone ProfileSectionId values.

Patch Changes

• The organization Security page now lists every enterprise SSO connection of the organization, each with its own status, domains, and actions. The SSO wizard edits one explicit connection, and a banner names it when the organization has more than one. Changing a provider or removing a connection now targets that connection instead of the first one returned by the API.

Minor Changes

• Introduce self-serve Directory Sync (SCIM) capabilities and related functionality.

• Add the SSO fallback sign-in flow to <SignIn />, for enterprise users the instance has allowlisted to sign in with an email code when they cannot reach their identity provider.

  For such a user the sign-in no longer redirects straight to the identity provider. It shows the SSO action — or the connection picker, when several connections serve the address — alongside a "Can't use SSO?" link leading to the standard email code step, which carries a notice that the organization requires single sign-on and that the attempt is recorded. Users without a fallback, and instances without the feature, are unaffected.

  Custom flows can read the same factor from the new ssoFallbackFirstFactors property on the sign-in resource. The flow adds the signIn.enterpriseSSO and signIn.ssoFallback localization keys and the ssoFallback card action element id.

Patch Changes

• Update tr-TR waitlist translations

• Improve Finnish translations

• Update Hebrew localization for OAuth consent messages

Minor Changes

• Add an authenticated OAuth device verification component and workflow hook for approving or denying OAuth Device Authorization Grant requests.

Patch Changes

• Display a proper message when a sign-in or invitation link is invalid or has expired. Previously these errors rendered the raw API copy "This ticket is invalid. Make sure you're using a valid ticket generated by Clerk.", which refers to Clerk implementation details that are meaningless to the end user signing in. The new messages are available under the unstable__errors.ticket_invalid_code and unstable__errors.ticket_expired_code localization keys.

Patch Changes

• Display a proper message when a password is rejected for matching one of the account's identifiers. Previously this error rendered as the incomplete sentence "Your password must contain ." on sign-up, reset password, and the user profile password form. The new message is available under the unstable__errors.form_password_matches_identifier localization key, and any password error the UI does not recognize now falls back to the message returned by the API instead of an empty sentence.

Patch Changes

• Add a "Back" action to the sign-in second-factor and client-trust steps, letting a stuck user abandon the attempt and return to the sign-in start.

Patch Changes

• Add support for configuring custom OpenID Connect enterprise connections through the Organization Profile.

• Expose whether an organization member has been deprovisioned, and mark deprovisioned members as inactive in the Organization Profile.