Add 403UserCentricPreparator to handle random parameters that generates a 403 error because the user is not allowed to browse them #55
+110
−3
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.
In many cases in the baseline we have to ignore some tests because the parameters in the URL are user centric.
This mean that if we change the item we request, the user gets a 403 (an not a 404), because they're not allowed to browse it.
So :
x-dummy
" parametersx-apitester-user-centric-parameter
that decide in the operation, if parameters are user centric or notIt will be used in the PR : https://github.com/simpleit/SdZv4/pull/14558
Example of usage :
/student-applications/{studentApplicationId}/disqualify
<- because the user is not allowed to browse student applications that are not his/users/{userId}/whatever
<- because only the right user can browse his own route.