Drop-OSS/drop
1
0
Fork 0
mirror of https://github.com/Drop-OSS/drop.git synced 2026-07-21 16:15:24 -04:00
Code Issues 77 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #418] Feature Request: Toggle off user creation minimum requirements #348

New Issue
Open
opened 2026-06-05 14:21:55 -04:00 by yindo · 0 comments
yindo commented 2026-06-05 14:21:55 -04:00
Owner
Copy Link
Copy Source

Originally created by @charredchar on GitHub (May 25, 2026).
Original GitHub issue: https://github.com/Drop-OSS/drop/issues/418

During the initial admin setup I am forced to use (quite arbitrary) requirements for most of the fields.
Personally I intend to use OIDC for users and admins later so these might not be an issue then but I prefer to set up an initial admin that is local to the service as a fallback. Requiring an email for something intended to be local is bizarre.
While I think having the requirements on by default isn't a problem it would be nice to allow disabling the forced email field, username and password length requirements. At least allow it via the compose as a variable that can be turned back on later but configuration in the admin panel would be nice, like for changing the length or complexity requirement for the password.

Originally created by @charredchar on GitHub (May 25, 2026). Original GitHub issue: https://github.com/Drop-OSS/drop/issues/418 During the initial admin setup I am forced to use (quite arbitrary) requirements for most of the fields. Personally I intend to use OIDC for users and admins later so these might not be an issue then but I prefer to set up an initial admin that is local to the service as a fallback. Requiring an email for something intended to be local is bizarre. While I think having the requirements on by default isn't a problem it would be nice to allow disabling the forced email field, username and password length requirements. At least allow it via the compose as a variable that can be turned back on later but configuration in the admin panel would be nice, like for changing the length or complexity requirement for the password.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
duplicate
feature
feature
good first issue
needs-triage
pull-request
Mirrored from GitHub Pull Request
 qol
support
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Drop-OSS/drop#348
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?