[SELC-4326] Feat: added check permission in operation with relationshipId #353
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
manuraf
previously approved these changes
Feb 20, 2024
|
|
To clarify the impact of the change introduced by the pull request, may you break down what an authenticated user was capable of doing before the PR that they shouldn't have been able to do? |
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.
List of Changes
Motivation and Context
Currently, on the APIs that performed updates on users using the relationship ID, there were no authorization checks. Therefore, it has become necessary to add a check upstream on the user's permissions to operate on such products.
How Has This Been Tested?
Screenshots (if appropriate):
Checklist: