Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Global configuration to prevent users from deleting their own account #1756

Closed
2 of 7 tasks
ghost opened this issue May 19, 2017 · 9 comments
Closed
2 of 7 tasks

Global configuration to prevent users from deleting their own account #1756

ghost opened this issue May 19, 2017 · 9 comments
Labels
type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first.
Milestone

Comments

@ghost
Copy link

ghost commented May 19, 2017

  • Gitea version (or commit ref):25d6e2a
  • Git version:2.11.2
  • Operating system:ubuntu/docker
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

There should be a default admin level configuration to prevent users from deleting their own account.

This has currently led to an issue on our installation, wherein, we use only the SMTP login source.
A user logs in once, admin sets their repo limit to 0.
The user deletes their account and signs back in, this is making the repo setting go back to -1 (unlimited)

This is just one problem.
We do not want any of the users of our ORG to have the ability to delete their own accounts for multiple other reasons as well.

@DblK
Copy link
Member

DblK commented May 19, 2017

I will try to work on it.
But first, I have some questions:

  1. Should it be linked to the authentification Source (Ex with LDAP EDIT)

image

  1. Or more simply add to the user modification page (in admin mode) with default value to prevent deletion

image

  1. Somewhere else?

@ghost
Copy link
Author

ghost commented May 19, 2017

My vote is for Approach 1

I would also like to suggest Approach 3, have a global variable in app.ini, so that it would apply to every source and prevent account deletion altogether.

Also, IMO, the administrator should have absolute authority over this and hence we should avoid placing any UI configurable element.

@DblK
Copy link
Member

DblK commented May 19, 2017

I will wait for comments from other members to see which implementation should be done.
The approach 3 sounds good too.

@lunny
Copy link
Member

lunny commented May 19, 2017

Maybe a global option to disable_user_suicide

@lunny lunny added type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first. labels May 19, 2017
@lunny lunny added this to the 1.x.x milestone May 19, 2017
@DblK
Copy link
Member

DblK commented May 19, 2017

When you said global option, you mean inside conf.ini?

@ghost
Copy link
Author

ghost commented May 19, 2017

I'm currently using the app.ini file to define gobal configuration variables.

@lunny
Copy link
Member

lunny commented May 20, 2017

@DblK yes

@lunny lunny removed this from the 1.x.x milestone Mar 20, 2023
@lunny
Copy link
Member

lunny commented Jun 20, 2023

should be resolved by #20549

@lunny
Copy link
Member

lunny commented Feb 27, 2024

Fixed by #29275

@lunny lunny closed this as completed Feb 27, 2024
@lunny lunny added this to the 1.22.0 milestone Feb 27, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 10, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

No branches or pull requests

2 participants