🎉 Introducing our March release: Create your ideal sign-up flow with multiple identifiers, connect with WordPress in minutes, and explore more updates!
Logto now supports configuring multiple required identifiers for user registration. This enhancement extends the previous single-identifier limitation, enabling a more comprehensive sign-up process.
Introduces a new optional field, secondaryIdentifiers, to the sign-in experience sign-up settings. This enhancement allows developers to specify multiple required user identifiers during the user sign-up process. Available options include email, phone, username and emailOrPhone.
Primary identifiers (signUp.identifiers):
[email, phone] allows either email OR phone registration, treated as a single requirement.Secondary identifiers (SignUp.secondaryIdentifiers):
emailOrPhone type: requires either email OR phone, treated as a single requirementExample 1: Username with required email and phone
usernameemail and phoneExample 2: Username with either email or phone
usernameemailOrPhoneExample 3: Email/phone with required username
email OR phoneusernameEnhanced sign-up configuration UI:
signUp.identifiers)signUp.secondaryIdentifiers)
We've relaxed several configuration constraints to give you more flexibility in customizing your authentication flows.
The password requirement is now optional when using username as a sign-up identifier. Please note, when configuring username as the sole sign-up identifier with password disabled, users will be unable to authenticate after registration. Ensure at least one of the following:
Removed the constraint requiring sign-up identifiers to be enabled as sign-in methods. We have fully decoupled the sign-up identifier settings from the sign-in methods. Developers can now require as many user identifiers as needed during the sign-up process without impacting the sign-in process.
Removed the requirement for password verification across all sign-in methods when password is enabled for sign-up.
In this release, we have transitioned the user sign-in experience from the legacy @logto/experience-legacy package to the latest @logto/experience package. This change fully adopts our new Experience API, enhancing the underlying architecture while maintaining the same user experience.
@logto/experience package by default.@logto/experience-legacy will be deprecated in future releases.Improve the OpenAI prompt to better support i18n plural form suffixes
make method isLanguageTag case-insensitive
Language tag case inconsistency was causing translation mismatches across packages:
@logto/phrases and @logto/phrases-experience: using lowercase tags (e.g., pt-br, zh-cn)@logto/language-kit: using mixed-case tags (e.g., pt-BR, zh-CN)Updated isLanguageTag function in language kit to be case-insensitive, ensuring:
scopes field to @logto/connector-azuread
client_id from token request body
client_id included in both request body and authentication headerclient_id from the request body while maintaining the authentication header, we ensure consistent behavior across different OIDC providers.