stricter handling of missing partyid #1092
Open
+119
−55
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
…the logged in user if no partyid was provided
|
/publish |
adamhaeger
added
the
bugfix
|
|
/publish |
PR release:
|
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.
Removed logic in stateless controller that would return the party of the logged in user if no partyid was provided.
Description
As noted in the comments of StatelessDataController.cs, if the client did not provide partyid, we would use the party of the logged in user.
This caused the error in the issue below.
This PR removes that fallback, we will now throw an error if the partyid is missing, or we cannot lookup instanceowner based on it.
Related Issue(s)
Verification