Replies: 2 comments 4 replies
|
I'm having an issue with new user provisioning due to this issue, but it's all users, not just guests. I do have an allowed domain and it's connected to entra, issue just started after 1.8.1 and the error is "Your email address has not been verified by Microsoft. Please verify your email an try signing in again." so it's related to the same change. The Mail attribute is set on my user accounts in Entra. I double checked the https://docs.getoutline.com/s/dfa77e56-d4d2-4b51-8ff8-84ea6608faa4 to see if there were any changes that needed to be done, but I don't see anything different than what I have setup. @songsid, is provisioning for non-guest accounts working for you still? |
|
@EddieTx For non-guest accounts on my end, provisioning still works fine — only accounts without the My workaround was to modify the email verification check directly in the Docker container ( |
Uh oh!
There was an error while loading. Please reload this page.
Description
The email verification check added in #12605 (v1.8.1) breaks sign-in for Azure AD accounts that lack the mail attribute — common with external/contractor accounts in enterprise tenants.
Problem
We use Azure AD SSO with contractor accounts. These accounts don't have the mail attribute set in Azure AD, so Microsoft returns
xms_edov = false. Combined with our allowed domains configuration, this causes the new check in userProvisioner to reject sign-in.
The Azure AD admin cannot modify the mail attribute for these external accounts. Other accounts with the mail attribute set work fine — only
those without it are affected.
Proposal
Add a toggle in Settings → Authentication to allow workspace admins to disable the email verification requirement:
This would be consistent with how allowed domains is already configurable in the admin UI.
Environment
All reactions