It's time for a new Logto release! This update brings 5 new social connectors, and some bug fixes.
cb2610: fix cli add offical connectors command missing connectors bug Fix the bug when running the cli commend logto connectors add --official, only 8 connectors are fetched from npm registry. This fix update logic to query additional pages of results when fetching connectors from the npm registry.
0b785e: display JWKS URI on application details page
e7accf: prevent i18n context contamination by using request-scoped instances This bug fix resolves a concurrency issue in i18n handling by moving from a global i18next instance to request-scoped instances.
When handling concurrent requests:
i18next instance's language was being modified via changeLanguage() calls.koaI18next middleware to create a cloned i18next instance for each request.ctx.i18n) All subsequent middleware and handlers should now use ctx.i18n instead of the global i18next instance.a5990ec57: fixes an incorrect condition check in the verification code flow where isNewIdentifier was using inverted logic for email and phone comparisons.
isNewIdentifier boolean logic to use identifier.value !== user.primaryEmail for email checksidentifier.value !== user.primaryPhoneThis fixes a regression where:
BindNewIdentifier templateUserPermissionValidation template28643c1f1: fix the email/phone identifier conflict handling logic during user registration.
When a user attempts to register with an email/phone that already exists:
"Sign in instead" modal will be shown when:
This caused an issue when:
Expected behavior: Show the "Email/phone already exists" error modal directly. If only password authentication is enabled. User should not be able to sign in with email/phone directly.
Shows the "Sign in instead" modal if:
Otherwise, shows the "Email/phone already exists" error modal directly.
bd18da4cf: properly filter WeChat connectors by platform (Web | Native) in SSR sign-in experience settings
Previously, platform-based social connector filtering was applied during the sign-in experience settings fetch process but not in the SSR sign-in experience data. As a result, platform-specific connectors were not correctly filtered when rendering the page using SSR data.
This update ensures that the same filtering logic is applied to SSR sign-in experience data, resolving the issue.
Affected connectors: WeChat Web and WeChat Native.