fix(connector): [BOA/Cybersource] Handle Invalid Api Secret #3485
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
SamraatBansal
previously approved these changes
Jan 30, 2024
ArjunKarthik
approved these changes
Jan 30, 2024
SamraatBansal
approved these changes
Jan 30, 2024
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.
Type of Change
Description
Server was throwing 5XX Error if wrong api_secret was passed during Payment Connector - Create.
This is now handled by throwing
InvalidConnectorConfigerror.Additional Changes
Motivation and Context
https://github.com/juspay/hyperswitch-cloud/issues/3255
How did you test it?
Testing can be done by adding wrong api_secret/api_key/key1 during Payment Connector - Create.
If wrong api_secret is added you should get the following error:
If wrong api_key/key1 is added you should get the following error:
Checklist
cargo +nightly fmt --allcargo clippy