[#IP-210] Add 403 to API specs where missing #125
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
balanza
requested review from
AleDore,
BurnedMarshal and
francescopersico
as code owners
Example of PR titles that include pivotal stories:
Generated by 🚫 dangerJS |
7 tasks
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.
Several APIs are exposed without explicitly declaring a 403 can happen, although they actually do. Mostly, this status can happen when the DevPortal user doesn't belong to the group allowed for such operaration.
Operations are:
submitMessageforUserWithFiscalCodeInBodysubmitMessageforUsergetMessagegetProfileByPOSTgetProfilegetSubscriptionsFeedForDatecreateServicegetUserServices