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

Auth / Capture Failures..?? #553

Closed
angelleye opened this Issue Sep 11, 2016 · 2 comments

Comments

Projects
None yet
2 participants
@angelleye
Owner

angelleye commented Sep 11, 2016

I have had a few reports of this happening from people, but then you tested and said it worked fine.

What's happening is that people are setting their order to be processed as Authorization, and that works fine. When they try to capture, though, they're getting an error that they don't have permissions to make the call.

I have another report of it now which confirms we must have something wrong.

The user submitted a ticket to PayPal MTS, and they confirmed that the DoCapture request we're sending does not contain any API credentials at all.

Of course, in our logs we're masking the API credentials, so we just see *** for those values in our logs. According to PayPal we're not actually sending anything for credentials in our DoCapture request, though, so we need to figure out what's going on there and be sure the credentials are included as necessary.

@angelleye angelleye added this to the 1.2.5 milestone Sep 11, 2016

@angelleye

This comment has been minimized.

Show comment
Hide comment
@angelleye

angelleye Nov 2, 2016

Owner

Here is another report of this happening.

I think our DoCapture request must be leaving the API credentials out entirely or something, but we can't tell that because our logs are masking with *** no matter what the value actually is.

On that note, we should add logic to our API log masks so that if the value is simply empty, then it leaves that way so we can see that. If it has any value, then go ahead and mask with ***.

Again, the previous calls are working fine with the credentials that are entered, but somehow the DoCapture is either pulling blank, or maybe pulling the wrong value (sandbox vs. live) for some reason..??

I think you've tested and it works for you in the sandbox, so it could even be a scenario where it doesn't happen unless you've got things set to live..??

Owner

angelleye commented Nov 2, 2016

Here is another report of this happening.

I think our DoCapture request must be leaving the API credentials out entirely or something, but we can't tell that because our logs are masking with *** no matter what the value actually is.

On that note, we should add logic to our API log masks so that if the value is simply empty, then it leaves that way so we can see that. If it has any value, then go ahead and mask with ***.

Again, the previous calls are working fine with the credentials that are entered, but somehow the DoCapture is either pulling blank, or maybe pulling the wrong value (sandbox vs. live) for some reason..??

I think you've tested and it works for you in the sandbox, so it could even be a scenario where it doesn't happen unless you've got things set to live..??

@angelleye angelleye modified the milestones: 1.2.5, 1.3.0 Nov 2, 2016

@angelleye

This comment has been minimized.

Show comment
Hide comment
@angelleye
Owner

angelleye commented Nov 17, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment