Use Logto as an OpenID Connect identity provider to build your app ecosystem; add authentication with two inputs with Protected App; and new guides for Blazor, SvelteKit, Nuxt.js, Expo (React Native), and Angular.
The long-awaited feature is finally here! You can now invite your team members to your Logto tenants. Collaborate with your team members to manage your applications, users, and other resources.
Invite your team members by following these steps:
Fill in the email address of the team member you want to invite, and choose the role you want to assign to them:
For more information, see Invite your team members.
You can now directly invoke a sign-in method by skipping the first screen. This is useful when you have a direct link to a sign-in method, for instance, when you have a "Sign in with Google" button on your website.
To use this feature, you need to pass the direct_sign_in parameter to the authentication request. It supports the following methods:
To learn more, see the Direct sign-in documentation.
Sign-in experience can be initiated with a specific screen by setting the first_screen parameter in the OIDC authentication request. This parameter is intended to replace the interaction_mode parameter, which is now deprecated.
See the First screen documentation for more information.
We have added support for the remaining OpenID Connect standard claims. Now, these claims are accessible in both ID tokens and the response from the /me endpoint.
Additionally, we adhere to the standard scopes - claims mapping. This means that you can retrieve most of the profile claims using the profile scope, and the address claim can be obtained by using the address scope.
For all newly introduced claims, we store them in the user.profile field.
In addition to the claims that Logto recognizes, all social connectors now also store the raw data returned by the social provider in the rawData field.
To access this data in a user object, you can use the user.identities.[idp-name].details.rawData field.
When migrating users from a legacy system to Logto, you can now use the passwordAlgorithm and passwordDigest fields in the POST /users API to store the user's original password hash.
Currently supported algorithms are:
When the user logs in, Logto will use the provided algorithm and digest to verify the password; if the verification succeeds, Logto will automatically migrate the password to the new Argon2 hash.
See API reference for more information.
avatar and customData fields in the POST /users API.GET /organization-roles can now be called with the q query parameter to filter the results by the role id, name, or description./interaction/consent endpoint 500 error.WKWebView of new iOS versions.@logto/connector-kit: [BREAKING] update SocialUserInfo and GetUserInfo types@logto/connector-kit: [BREAKING] guard results of parseJson and parseJsonObjectWe are working on the following features: