starred/documenso

Fork 0

mirror of https://github.com/documenso/documenso.git synced 2026-04-26 06:15:58 +03:00

[GH-ISSUE #2385] UNVERIFIED_EMAIL error when using Microsoft OIDC #668

New issue

Open

opened 2026-02-26 18:47:59 +03:00 by kerem · 3 comments

kerem commented

2026-02-26 18:47:59 +03:00

Owner

Originally created by @tleclair-web on GitHub (Jan 13, 2026).
Original GitHub issue: https://github.com/documenso/documenso/issues/2385

Issue Description

Hello,

This is what I get when configuring Microsoft OIDC on self hosted community deployment:

{
  "code": "UNVERIFIED_EMAIL",
  "message": "Account email is not verified"
}

Steps to Reproduce

Configure Microsoft OIDC:

NEXT_PRIVATE_MICROSOFT_CLIENT_ID="<REDACTED>"
NEXT_PRIVATE_MICROSOFT_CLIENT_SECRET="<REDACTED>"

Try to register or log in (both give same result) using Microsoft 365.
You get the error message described above.

Enabling NEXT_PRIVATE_OIDC_SKIP_VERIFY="true" didn't change anything to the issue.

Expected Behavior

I should be able to bypass email verification, or to receive a checking email.

Current Behavior

No response

Screenshots (optional)

No response

Operating System [e.g., Windows 10]

Any

Browser [e.g., Chrome, Firefox]

Any

Version [e.g., 2.0.1]

2.3.0

Please check the boxes that apply to this issue report.

I have searched the existing issues to make sure this is not a duplicate.
I have provided steps to reproduce the issue.
I have included relevant environment information.
I have included any relevant screenshots.
I understand that this is a voluntary contribution and that there is no guarantee of resolution.
I want to work on creating a PR for this issue if approved

Originally created by @tleclair-web on GitHub (Jan 13, 2026). Original GitHub issue: https://github.com/documenso/documenso/issues/2385 ### Issue Description Hello, This is what I get when configuring Microsoft OIDC on self hosted community deployment: ```json { "code": "UNVERIFIED_EMAIL", "message": "Account email is not verified" } ``` ### Steps to Reproduce Configure Microsoft OIDC: ```sh NEXT_PRIVATE_MICROSOFT_CLIENT_ID="<REDACTED>" NEXT_PRIVATE_MICROSOFT_CLIENT_SECRET="<REDACTED>" ``` Try to register or log in (both give same result) using Microsoft 365. You get the error message described above. Enabling `NEXT_PRIVATE_OIDC_SKIP_VERIFY="true"` didn't change anything to the issue. ### Expected Behavior I should be able to bypass email verification, or to receive a checking email. ### Current Behavior _No response_ ### Screenshots (optional) _No response_ ### Operating System [e.g., Windows 10] Any ### Browser [e.g., Chrome, Firefox] Any ### Version [e.g., 2.0.1] 2.3.0 ### Please check the boxes that apply to this issue report. - [x] I have searched the existing issues to make sure this is not a duplicate. - [x] I have provided steps to reproduce the issue. - [x] I have included relevant environment information. - [ ] I have included any relevant screenshots. - [x] I understand that this is a voluntary contribution and that there is no guarantee of resolution. - [ ] I want to work on creating a PR for this issue if approved

kerem added the

status: triage

label

2026-02-26 18:47:59 +03:00

kerem commented

2026-02-26 18:48:00 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jan 13, 2026):

Thank you for opening your first issue and for being a part of the open signing revolution!

One of our team members will review it and get back to you as soon as it possible 💚

Meanwhile, please feel free to hop into our community in Discord

@github-actions[bot] commented on GitHub (Jan 13, 2026): Thank you for opening your first issue and for being a part of the open signing revolution! <br /> One of our team members will review it and get back to you as soon as it possible 💚 <br /> Meanwhile, please feel free to hop into our community in [Discord](https://documen.so/discord)

kerem commented

2026-02-26 18:48:00 +03:00

Author

Owner

@MakakWasTaken commented on GitHub (Jan 13, 2026):

The issue seems to be that this settings is false:
github.com/documenso/documenso@db913e95b6/packages/auth/server/config.ts (L26)

This should either be set to true or the email verification flow should be activated on sign in.
An environment variable to bypass this would be nice. Something like NEXT_PRIVATE_MICROSOFT_BYPASS_EMAIL_VERIFICATION="true"

@MakakWasTaken commented on GitHub (Jan 13, 2026): The issue seems to be that this settings is false: https://github.com/documenso/documenso/blob/db913e95b6719a51284597cd6cc5b1d40ef1aa4a/packages/auth/server/config.ts#L26 This should either be set to `true` or the email verification flow should be activated on sign in. An environment variable to bypass this would be nice. Something like `NEXT_PRIVATE_MICROSOFT_BYPASS_EMAIL_VERIFICATION="true"`

kerem commented

2026-02-26 18:48:00 +03:00

Author

Owner

@tleclair-web commented on GitHub (Jan 13, 2026):

Thanks for your reply, this is interesting. I think indeed a variable to skip email verification would be nice !

@tleclair-web commented on GitHub (Jan 13, 2026): Thanks for your reply, this is interesting. I think indeed a variable to skip email verification would be nice !

kerem referenced this issue

2026-02-26 19:31:53 +03:00

[PR #668] [CLOSED] fix: update validation message of clear signature input #1114

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/documenso#668

No description provided.

Rows
Columns