fix(rest.identity): adding specific error messages when user is not found #5047
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
...provider/src/main/java/org/eclipse/kura/internal/rest/identity/provider/IdentityService.java
Outdated
Show resolved
Hide resolved
salvatore-coppola
approved these changes
Dec 12, 2023
Signed-off-by: SimoneFiorani <[email protected]>
Signed-off-by: SimoneFiorani <[email protected]>
Signed-off-by: SimoneFiorani <[email protected]>
Signed-off-by: SimoneFiorani <[email protected]>
Signed-off-by: SimoneFiorani <[email protected]>
salvatore-coppola
force-pushed
the
rest-identity-error-adding
branch
from
5b3c668 to
bf89c81
Compare
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.
This PR adds a more exhaustive response when an user tries to execute the following REST APIs:
with a non-existing
userNamein the request json.Before this variation, an unspecific message would have been received, whic could be misleading.
Related Issue:
Description of the solution adopted:
Screenshots:
Manual Tests:
Any side note on the changes made: