starred/documenso

Fork 0

mirror of https://github.com/documenso/documenso.git synced 2026-04-25 22:05:59 +03:00

[GH-ISSUE #1272] NEXT_PRIVATE_OIDC_SKIP_VERIFY - ignored #355

New issue

Closed

opened 2026-02-26 18:46:39 +03:00 by kerem · 6 comments

kerem commented

2026-02-26 18:46:39 +03:00

Owner

Originally created by @mnbro on GitHub (Aug 8, 2024).
Original GitHub issue: https://github.com/documenso/documenso/issues/1272

Originally assigned to: @ephraimduncan on GitHub.

Issue Description

My understanding is that setting NEXT_PRIVATE_OIDC_SKIP_VERIFY to true will skip mail verification for an OIDC authenticated user.

If the above assumption is true, this is not the case. The OIDC user is still required to be verified by email.

Steps to Reproduce

No response

Expected Behavior

No response

Current Behavior

No response

Screenshots (optional)

No response

Operating System [e.g., Windows 10]

No response

Browser [e.g., Chrome, Firefox]

No response

Version [e.g., 2.0.1]

1.6

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 @mnbro on GitHub (Aug 8, 2024). Original GitHub issue: https://github.com/documenso/documenso/issues/1272 Originally assigned to: @ephraimduncan on GitHub. ### Issue Description My understanding is that setting `NEXT_PRIVATE_OIDC_SKIP_VERIFY` to `true` will skip mail verification for an OIDC authenticated user. If the above assumption is true, this is not the case. The OIDC user is still required to be verified by email. ### Steps to Reproduce _No response_ ### Expected Behavior _No response_ ### Current Behavior _No response_ ### Screenshots (optional) _No response_ ### Operating System [e.g., Windows 10] _No response_ ### Browser [e.g., Chrome, Firefox] _No response_ ### Version [e.g., 2.0.1] 1.6 ### 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

2026-02-26 18:46:39 +03:00

closed this issue
added the
Stale

status: triage
labels

kerem commented

2026-02-26 18:46:40 +03:00

Author

Owner

@ephraimduncan commented on GitHub (Sep 21, 2024):

Hello @mnbro, I've not been able to reproduce this.

Could you provide more details about your setup, the OIDC provider, and any error logs you encountered?

@ephraimduncan commented on GitHub (Sep 21, 2024): Hello @mnbro, I've not been able to reproduce this. Could you provide more details about your setup, the OIDC provider, and any error logs you encountered?

kerem commented

2026-02-26 18:46:40 +03:00

Author

Owner

@mnbro commented on GitHub (Sep 23, 2024):

Hi @ephraimduncan,

Could you please set the following environment variables:

NEXT_PRIVATE_OIDC_ALLOW_SIGNUP="true"
NEXT_PRIVATE_OIDC_SKIP_VERIFY="true"
NEXT_PUBLIC_DISABLE_SIGNUP="true"

After configuring these, are you able to sign in? Additionally, is email verification still required?

Thank you!

@mnbro commented on GitHub (Sep 23, 2024): Hi @ephraimduncan, Could you please set the following environment variables: ```env NEXT_PRIVATE_OIDC_ALLOW_SIGNUP="true" NEXT_PRIVATE_OIDC_SKIP_VERIFY="true" NEXT_PUBLIC_DISABLE_SIGNUP="true" ``` After configuring these, are you able to sign in? Additionally, is email verification still required? Thank you!

kerem commented

2026-02-26 18:46:40 +03:00

Author

Owner

@ephraimduncan commented on GitHub (Sep 23, 2024):

I was able to sign in successfully without email verification being required. These were the steps I used.

Performed a fresh installation of Documenso with a clean local database
Set up OIDC with Auth0, including:
- Manually added a user in Auth0 with an email (not verified) and password
- Configured the environmental variables as above.

Could you let me know which version of Documenso you're currently using? If you're not on the latest version, try updating and let us know if the issue persists.

@ephraimduncan commented on GitHub (Sep 23, 2024): I was able to sign in successfully without email verification being required. These were the steps I used. 1. Performed a fresh installation of Documenso with a clean local database 2. Set up OIDC with Auth0, including: - Manually added a user in Auth0 with an email (not verified) and password - Configured the environmental variables as above. Could you let me know which version of Documenso you're currently using? If you're not on the latest version, try updating and let us know if the issue persists.

kerem commented

2026-02-26 18:46:40 +03:00

Author

Owner

@mnbro commented on GitHub (Sep 24, 2024):

I was able to sign in successfully without email verification being required. These were the steps I used.

Performed a fresh installation of Documenso with a clean local database

Set up OIDC with Auth0, including:

Manually added a user in Auth0 with an email (not verified) and password

Configured the environmental variables as above.

Could you let me know which version of Documenso you're currently using? If you're not on the latest version, try updating and let us know if the issue persists.

I am using 1.6. Are you able to reproduce it on this version?

@mnbro commented on GitHub (Sep 24, 2024): > I was able to sign in successfully without email verification being required. These were the steps I used. > > 1. Performed a fresh installation of Documenso with a clean local database > 2. Set up OIDC with Auth0, including: > > * Manually added a user in Auth0 with an email (not verified) and password > * Configured the environmental variables as above. > > Could you let me know which version of Documenso you're currently using? If you're not on the latest version, try updating and let us know if the issue persists. I am using 1.6. Are you able to reproduce it on this version?

kerem commented

2026-02-26 18:46:40 +03:00

Author

Owner

@maximelehericy commented on GitHub (Mar 25, 2025):

@mnbro that is fixed for me in v1.9.1-rc.9.

@maximelehericy commented on GitHub (Mar 25, 2025): @mnbro that is fixed for me in v1.9.1-rc.9.

kerem commented

2026-02-26 18:46:40 +03:00

Author

Owner

@ephraimduncan commented on GitHub (Aug 23, 2025):

This issues has been fixed.

@ephraimduncan commented on GitHub (Aug 23, 2025): This issues has been fixed.

kerem referenced this issue

2026-02-26 19:30:58 +03:00

[PR #355] [CLOSED] feat: Payments #904

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#355

No description provided.

Rows
Columns