Add trust unverified email settings to Azure OIDC SSO connector.
Context
Since we launched the EntraID OIDC SSO connector we have received several feedbacks that their customer's email address can not be populated to Logto's user profile when signing up through the EntraID OIDC SSO connector.
The root cause is that Logto only syncs trusted email addresses with email_verified claim present in the OIDC userinfo response.
However, for EntraID, the user email address is manually management by admin users. Those emails are not verified-guaranteed. So as a result when connecting EntraID through an OIDC-based SSO connector, the email_verified claim will not be returned.
As a work around, we add this extra trustUnverifiedEmail config field for the EntraID OIDC connector. Developers may choose to always trust those emails returned from the Azure Directory at their own risk.
Summary
Add trust unverified email settings to Azure OIDC SSO connector.
Context
Since we launched the EntraID OIDC SSO connector we have received several feedbacks that their customer's email address can not be populated to Logto's user profile when signing up through the EntraID OIDC SSO connector. The root cause is that Logto only syncs trusted email addresses with
email_verified
claim present in the OIDC userinfo response. However, for EntraID, the user email address is manually management by admin users. Those emails are not verified-guaranteed. So as a result when connecting EntraID through an OIDC-based SSO connector, theemail_verified
claim will not be returned. As a work around, we add this extratrustUnverifiedEmail
config field for the EntraID OIDC connector. Developers may choose to always trust those emails returned from the Azure Directory at their own risk.Testing
test locally
Checklist
.changeset