We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When Authentication call fails, 200 status code is returned. This should be 4xx.
When Authentication call fails, 4xx status code should be returned.
When Authentication call fails, 200 status code is returned.
Provide an unambiguous set of steps to reproduce this bug. Include code or configuration to reproduce, if relevant.
No response
Are you using hyperswitch hosted version? Yes/No If yes, please provide the value of the x-request-id response header to help us debug your issue.
x-request-id
If not (or if building/running locally), please provide the following details:
rustc --version
cargo r --features vergen -- --version
Yes, I am willing to submit a PR!
The text was updated successfully, but these errors were encountered:
hrithikesh026
Successfully merging a pull request may close this issue.
Bug Description
When Authentication call fails, 200 status code is returned. This should be 4xx.
Expected Behavior
When Authentication call fails, 4xx status code should be returned.
Actual Behavior
When Authentication call fails, 200 status code is returned.
Steps To Reproduce
Provide an unambiguous set of steps to reproduce this bug. Include code or configuration to reproduce, if relevant.
Error response is returned with 200 status code.
Context For The Bug
No response
Environment
Are you using hyperswitch hosted version? Yes/No
If yes, please provide the value of the
x-request-id
response header to help us debug your issue.If not (or if building/running locally), please provide the following details:
rustc --version
): ``cargo r --features vergen -- --version
): ``Have you spent some time checking if this bug has been raised before?
Have you read the Contributing Guidelines?
Are you willing to submit a PR?
Yes, I am willing to submit a PR!
The text was updated successfully, but these errors were encountered: