🎉 Introducing our June release: Account API for Passkeys, access user interaction details in custom JWT, and more updates!
You can now manage WebAuthn passkeys in Account API, including:
We have implemented Related Origin Requests so that you can manage the WebAuthn passkeys on your website which has a different domain from the Logto's sign-in page.
To learn more, check out the documentation.
User interaction data is now accessible through the context.interaction when generating custom token claims:
| Property | Description | Type |
|---|---|---|
interactionEvent | The interaction event of the current user interaction | SignIn or Register |
userId | The user id of the current user interaction | string |
verificationRecords | A list of verification records submitted by the user to identify and verify their identity during interactions. | VerificationRecord[] |
Example Use Case:
Read the verification records from the interaction context. If an Enterprise SSO verification record is present, include the corresponding user profile from the Enterprise SSO identities as additional token claims.
See custom token claims context for more details.
updated_at field to user_sso_identities tableLegacy hashing algorithm such as SHA512access_token optional for Azure OIDC SSO connector, previously, the Azure OIDC connector strictly required an access token in the token response, which caused issues with Azure B2C applications that only return ID tokens.