Skip to content
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

[BUG] When Authentication call fails, 200 status code is returned #4391

Open
2 tasks done
hrithikesh026 opened this issue Apr 18, 2024 · 0 comments · May be fixed by #4388
Open
2 tasks done

[BUG] When Authentication call fails, 200 status code is returned #4391

hrithikesh026 opened this issue Apr 18, 2024 · 0 comments · May be fixed by #4388
Assignees
Labels
C-bug Category: Bug S-awaiting-triage Status: New issues that have not been assessed yet

Comments

@hrithikesh026
Copy link
Contributor

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.

  1. Create a merchant with checkout payment connector and threedsecure.io authentication connector.
  2. Create a payment with 3ds enabled and external threeds.
  3. Authenticate without doing 3ds method data collection.
    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:

  1. Operating System or Linux distribution:
  2. Rust version (output of rustc --version): ``
  3. App version (output of cargo r --features vergen -- --version): ``

Have you spent some time checking if this bug has been raised before?

  • I checked and didn't find a similar issue

Have you read the Contributing Guidelines?

Are you willing to submit a PR?

Yes, I am willing to submit a PR!

@hrithikesh026 hrithikesh026 added C-bug Category: Bug S-awaiting-triage Status: New issues that have not been assessed yet labels Apr 18, 2024
@hrithikesh026 hrithikesh026 self-assigned this Apr 18, 2024
@hrithikesh026 hrithikesh026 linked a pull request Apr 18, 2024 that will close this issue
15 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category: Bug S-awaiting-triage Status: New issues that have not been assessed yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant