-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Critical ErrorResult #140
Comments
EnochMtzR
added a commit
to EnochMtzR/Result
that referenced
this issue
Jun 16, 2023
ardalis
pushed a commit
that referenced
this issue
Sep 12, 2023
ardalis
added a commit
that referenced
this issue
Sep 13, 2023
* Added CriticalError to ResultStatuses (#140) * Updated tests --------- Co-authored-by: JosnocSackra <[email protected]> Co-authored-by: AVANADE-CORP\r.bajor <[email protected]> Co-authored-by: Steve Smith <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Specific Case:
The Issue:
Currently, there is no
ResultStatus
that may be mapped to the500
error code since theError
ResultStatus
maps (quite rightly, in my opinion) to a422
Unprocessable
error code.However, I have the following specific case:
The
UserIdCannotBeRetireved
exception is thrown when the IDP did not set thesub
claim. This, in my opinion, is a critical error and should return anInternalServerError
(status500
) since this is not an issue with anything the user has done.The Proposal:
A new
CriticalError
ResultStatus
that maps to anInternalServerError
(500
) status code.I have a pull request with my take on this issue: #141
The text was updated successfully, but these errors were encountered: