Deactivate/update user #174
Merged
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
alainbodiguel
requested review from
sebbousquet,
mbarbet,
MohamedHamouGisaia,
sylvaingaudan and
QuCMGisaia
MohamedHamouGisaia
approved these changes
May 3, 2024
arlas-iam-rest/src/main/java/io/arlas/iam/rest/service/IAMRestService.java
Outdated
Show resolved
Hide resolved
| @@ -465,7 +470,17 @@ public void test903DeleteUserNotSelf() { | |||
| } | |||
|
|
|||
| @Test | |||
| public void test904DeleteUserSelf() { | |||
| public void test904DeactivateUser() { | |||
There was a problem hiding this comment.
what happens if a user deactivate/activate itself ?
There was a problem hiding this comment.
he'll have to ask an administrator to reactivate him
sebbousquet
approved these changes
May 3, 2024
alainbodiguel
force-pushed
the
feat/deactivateUser
branch
from
b3f826b to
b3d5a5c
Compare
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fix #173