-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
feat(v2): Added Ephemeral auth for v2 #6813
base: main
Are you sure you want to change the base?
Conversation
@@ -251,6 +261,11 @@ pub async fn payment_method_delete_api( | |||
}) | |||
.into_inner(); | |||
|
|||
let auth = match auth::is_ephemeral_auth(req.headers()) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is api-key based auth and not ephemeral_auth
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should our SDK not handle the delete API? Will the SDK not support delete API or will there be a callback to merchant for this?
@@ -224,6 +229,11 @@ pub async fn payment_method_retrieve_api( | |||
}) | |||
.into_inner(); | |||
|
|||
let auth = match auth::is_ephemeral_auth(req.headers()) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is reason to make retrieve as ephemeral_auth?
Remove ephemeral_auth, this should be only api-key based auth.
Type of Change
Description
This PR contains -
Additional Changes
Motivation and Context
How did you test it?
Response
Response -
Response -
Response -
Response -
Response -
Can use the ephemeral key obtained here to hit the above APIs
Checklist
cargo +nightly fmt --all
cargo clippy