add "disable user" feature #24501
Closed
add "disable user" feature #24501
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
initMountPoints is marking a user as successfully initialized too early. If the user was not found an NoUserException was thrown, the second time initMountPoints is called would not rethrow the exception and happily continue. This fix makes sure that we consistently throw NoUserException when initMountPoints is called repeatedly with invalid users.
App migration steps need to push feedback to the user ....
bring back CRUDS permissions for federated shares
dont do optimized size propagation for encrypted files
* Also moved the autoloader setup a bit up since we need it in initpaths
…hibboleth Disable web updater if ldap or shibboleth are installed
Move \OC\AppFramework to PSR-4
…ernotfoundagain Mark $usersSetup only if user was found in initMountPoints
Because some people do not think…
Move \OC\Encryption to PSR-4
Add link to security page
Deprecate appinfo/update.php - RepairSteps within info.xml are to be …
For one, it solves potential conflicts when using the resource. For the other, one on the login check (the only place where a clone happens currently) we do not need to rebind after confirming the user's login was successful.
Move \OC\SystemTag to PSR-4
Move \OC\Files to PSR-4
…gs_to_app move federated sharing settings to the federatedfilesharing app
Move \OCP\Activity to PSR-4
Cache shareManager
Move \OCP\App to PSR-4
Move \OCP\AppFramework to PSR-4
Move \OCP\BackgroundJob to PSR-4
Move \OCP\Capabilities to PSR-4
Set higher timeout limit
wording in LDAP wizard
Timeout was increased but tests were not updated.
Fix unit tests broken after #24457
Wait a while even after successful conect ...
Allow migration steps to use automatic DI
New animated loader: full css
|
Thanks a lot for your contribution! Alternatively you can add a comment here where you state that this contribution is MIT licensed. Some more details about out pull request workflow can be found here: http://owncloud.org/code-reviews-on-github/ |
|
@kenyang001, the "disable user" feature was already developed on 9.1, see #23844 |
|
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
when users left company, i think the "disable user" feature is really necessary.
1, we don't want to reset the user's password, as our owncloud has encryption plugin enabled.
2, we don't want to delete his owncloud account immediately, as his owncloud has working files.
to avoid abuse usages, we are really looking forward to the "disable user" feature. thanks.