🚀 OIDC step-up authentication, Sign-In with Ethereum, the iOS Save
Password prompt, and self-service personal access tokens.
Hi [First name],
Logto v1.46.0 is out, bringing OIDC step-up authentication, Sign-In
with Ethereum, a way to keep the iOS Save Password prompt, and
self-service personal access tokens, along with GeeTest CAPTCHA,
SAML static attributes, and a round of security hardening.
Here's what's new.
OIDC step-up authentication
Apps can now require a recent or stronger sign-in before sensitive
actions, using standard OIDC parameters.
-
Pass
acr_values and max_age in the
authorization request, then read acr,
amr, and auth_time from ID tokens,
access tokens, and introspection responses.
-
Account Center now authorizes sensitive Account API operations
with a fresh first-party access token. When the sign-in isn't
recent enough, the Account API answers with an RFC 9470 step-up
challenge.
-
Set how recent the sign-in must be under
Console > Sign-in experience > Account center > Recent
authentication
(10 minutes by default).
-
Apps that call the Account API directly can keep using a
verification record ID for sensitive operations.
Sign-In with Ethereum
The new Ethereum Wallet social connector lets users sign in with an
EVM wallet. Users with a browser wallet sign a one-time Sign-In with
Ethereum (EIP-4361) message without leaving the sign-in page. One
address works across supported EVM chains, and admins can restrict
the allowed chain IDs.
Keep the iOS Save Password prompt
On iOS, ASWebAuthenticationSession closes as soon as it
sees the app's callback URL, which dismisses the system
"Save Password" prompt right after a password sign-in.
Pass the new confirm_redirect_policy=password sign-in
parameter to show a "Continue" page after the user enters
a password. The page returns to the app only when the user selects
"Continue", so the prompt stays on screen. The Swift
integration guide in Console shows how to use it.
Self-service personal access tokens
When personal access tokens are turned on in Account Center, users
can create, rename, and revoke their own tokens on the Account
Center Security page. Each token is shown only once
at creation and expires within 365 days. The same operations are
available through the Account API with the new
urn:logto:scope:personal_access_tokens scope.
More sign-in and admin controls
-
GeeTest CAPTCHA: GeeTest CAPTCHA v4 is now
available under
Console > Security > CAPTCHA, a good fit
for sign-in experiences targeting mainland China.
-
Require MFA setup for a user: Turn it on from the
user details page or with
mfa.required in the
Management API. The user must set up MFA on their next sign-in.
-
Unlock a user: Clear all sign-in and security
verification lockouts for a user from the user details page.
-
SHA-crypt password import: Migrate users with
$5$ and
$6$ password hashes using the
Legacy password algorithm.
-
SAML static attributes: Send fixed values, such
as an account or site ID, in every SAML assertion.
-
Cross-Origin-Opener-Policy for Bring your UI:
Choose
same-origin-allow-popups or
same-origin for hosted sign-in pages that serve your
custom UI.
-
access_denied when sign-in is cancelled:
Cancelling the consent page, or a failed direct sign-in,
now returns the user to the app with access_denied.
-
login_hint for Account Center:
Pre-fill the identifier when users need to sign in to
Account Center.
Management API and webhooks
-
Search users by custom data with the repeatable
customData query parameter on
GET /api/users.
-
Find the organizations a user would be provisioned into with the
jitEmailDomain query parameter on
GET /api/organizations.
-
GET /api/organizations/:id/users now shows whether
each member has a password set.
-
Every webhook payload now carries a
deliveryId that
stays the same across retries, so receivers can process each
delivery exactly once.
Security hardening
This release includes security fixes across MFA, social and
enterprise sign-in, the Account API, and Logto Tunnel.
-
Action required: the standard OAuth 2.0 social
connector adds a
Disable Email Sync switch, matching the Microsoft
Azure AD connector. Upgrading alone does not change how existing
connectors behave, so review every OAuth 2.0 and Azure AD social
connector and turn the switch on when the provider does not verify
that users own the email addresses it returns.
-
The Apple connector now takes the user's email only from the
Apple ID token, and returns no email when Apple marks it as
unverified.
-
User-level and organization-level MFA requirements now take
precedence over account settings that turn MFA off or skip it, and
MFA verifications are bound to the account they were created for.
-
SAML enterprise SSO connectors now accept an assertion only when
its audience exactly matches the connector's Audience URI (SP
Entity ID).
-
Retrieving stored social or enterprise SSO provider tokens, and
reading backup codes, sessions, grants, and trusted devices
through the Account API, now require a first-party application.
-
Authorization codes, device codes, pushed authorization requests,
and one-time tokens are now strictly single-use.
Other improvements and fixes
-
The sign-in page no longer loads blank on iOS and Safari versions
earlier than 16.4.
-
Social sign-in errors are clearer: an unreachable provider returns
a 502, a declined authorization returns a 401 with the
provider's error, and connector errors show the
provider's actual message.
-
Refresh token requests from clients such as OpenAI Codex that send
a space-padded
scope no longer fail with invalid_scope,
so users stay signed in.
-
Creating or updating an application now rejects unknown
customClientMetadata keys, so typos no longer pass
silently.
-
The Patreon connector moves to Patreon API v2, so Patreon sign-in
works again.
-
The Swift integration guide now uses a consistent client name in
its code examples.
Self-hosting notes
-
The official Docker image now runs on Node.js 26. Logto supports
Node.js 22, 24, and 26, with minimum versions 22.23.4, 24.22.1,
and 26.12.1.
-
This release ships database alterations. Run the database
alteration command before starting the new version.
-
Core and the CLI database commands now retry the database
connection on DNS failures instead of exiting immediately.
Thanks to community contributors
@nicolaj0,
@RaphaelFakhri,
@mvanhorn, and
@timokoethe for their
work in this release.
Try these new features now
As always, we welcome your feedback and suggestions. Feel free to
reach out if you have any questions or need assistance.
|