Logto
Day 29 after signup
Logto product updates
🚀 OIDC step-up authentication, Sign-In with Ethereum, the iOS Save Password prompt, and self-service personal access tokens.
Why it works
- Lead with a concise release summary so readers can quickly understand the update's main themes.
- Group changes under descriptive headings, making a long technical update easier to scan.
- Put the action-required security guidance within the relevant release section so readers can act on it in context.
How it is built
- Release overview
- Major feature details
- Additional controls
- API and webhook changes
Email copy
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 A