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

Allow disabling of a single user #23838

Closed
rullzer opened this issue Apr 7, 2016 · 4 comments · Fixed by #23844
Closed

Allow disabling of a single user #23838

rullzer opened this issue Apr 7, 2016 · 4 comments · Fixed by #23844

Comments

@rullzer
Copy link
Contributor

rullzer commented Apr 7, 2016

To migrate users from one storage to the next without bringing down the whole system we must be able to disable single users.

This would then block out the users so we can safely transfer their data.
Ideally we make sure this is not to distruptive by throwing a 503 for shares from this user for example.

@DeepDiver1975 assigned to you as discussed.

@DeepDiver1975
Copy link
Member

@LukasReschke should we add you idea regarding the version number to invalidate sessions into this?

DeepDiver1975 added a commit that referenced this issue Apr 7, 2016
@DeepDiver1975 DeepDiver1975 changed the title Allow disabling of a single user Allow disabling of a single user Apr 7, 2016
@ghost
Copy link

ghost commented Apr 7, 2016

Existing issue for the User Management: #12601

@DeepDiver1975
Copy link
Member

@RealRancor THX for keeping the mess sorted out! 😉

DeepDiver1975 added a commit that referenced this issue Apr 8, 2016
DeepDiver1975 added a commit that referenced this issue May 2, 2016
@lock
Copy link

lock bot commented Aug 4, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Aug 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants