starred/documenso

Fork 0

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

[GH-ISSUE #1271] OIDC user not being provisioned #357

New issue

Closed

opened 2026-02-26 18:46:39 +03:00 by kerem · 2 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/1271

Originally assigned to: @ephraimduncan on GitHub.

Issue Description

For a fresh install I setup OIDC and NEXT_PUBLIC_DISABLE_SIGNUP="true" and NEXT_PRIVATE_OIDC_ALLOW_SIGNUP="true".

A new OIDC user successfully authenticates but will not be provisioned (the app will redirect him to user not found page).

The only way to fix the above is to set NEXT_PUBLIC_DISABLE_SIGNUP="false" and after the user is provisioned set it back to true.

Steps to Reproduce

No response

Expected Behavior

An OIDC user should be provisioned if NEXT_PUBLIC_DISABLE_SIGNUP="true" and NEXT_PRIVATE_OIDC_ALLOW_SIGNUP="true"

Current Behavior

OIDC user is not provisioned.

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/1271 Originally assigned to: @ephraimduncan on GitHub. ### Issue Description For a fresh install I setup OIDC and `NEXT_PUBLIC_DISABLE_SIGNUP="true"` and `NEXT_PRIVATE_OIDC_ALLOW_SIGNUP="true"`. A new OIDC user successfully authenticates but will not be provisioned (the app will redirect him to user not found page). The only way to fix the above is to set `NEXT_PUBLIC_DISABLE_SIGNUP="false"` and after the user is provisioned set it back to `true`. ### Steps to Reproduce _No response_ ### Expected Behavior An OIDC user should be provisioned if `NEXT_PUBLIC_DISABLE_SIGNUP="true"` and `NEXT_PRIVATE_OIDC_ALLOW_SIGNUP="true"` ### Current Behavior OIDC user is not provisioned. ### 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

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

The old NextAuth implementation had the NEXT_PRIVATE_OIDC_ALLOW_SIGNUP functionality, but it wasn't carried over to the new auth implementation.

The current OIDC implementation in creates new users without checking for NEXT_PUBLIC_DISABLE_SIGNUP, so OIDC users should be provisioned regardless.

@ephraimduncan commented on GitHub (Aug 23, 2025): The old NextAuth implementation had the `NEXT_PRIVATE_OIDC_ALLOW_SIGNUP` functionality, but it wasn't carried over to the new auth implementation. The current OIDC implementation in creates new users without checking for `NEXT_PUBLIC_DISABLE_SIGNUP`, so OIDC users should be provisioned regardless.

kerem referenced this issue

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

[PR #357] [MERGED] feat: universal upload #907

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

No description provided.

Rows
Columns