-
Notifications
You must be signed in to change notification settings - Fork 260
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
oAuth Bad Request #34
Comments
Per my message in our forums, I'm closing out this issue in favor of the open support ticket you created. |
For reference can you link to the forum post? I'm having similar issues, and this ranks high on Google for "zendesk oauth bad request 400" |
https://support.zendesk.com/entries/99230886-PHP-wrapper-oAuth-issue The post was also closed without any answer. My support ticket was created a week ago, and Zendesk is yet to assign someone. |
@duellsy I'd encourage you to submit a ticket to our Support team with details about the requests you're making that trigger a 400 response so that our Support team can investigate. We aren't aware of any systemic issues with the client itself at this time, so we'll need to troubleshoot with you. |
@nCrafts What is your ticket number? I can take a look and see where it is at. |
Ben, 832729 -- On 4 September 2014 at 11:24:18 pm, Ben Evans (notifications@github.com) wrote: @nCrafts What is your ticket number? I can take a look and see where it is at. — |
@sbkinney I was able to sort out my issue, when requesting the token I had to not encode the callback url, then all worked fine. |
I am trying the example in oauth.php. I am able to get the authorisation code, but when I get redirected back to exchange the code for the token, I get this error:
The text was updated successfully, but these errors were encountered: