-
-
Notifications
You must be signed in to change notification settings - Fork 106
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
OAuth2 - Method not allowed (405) when getting the access Token #386
Comments
Hey @labomatik I'm sorry for the delay in getting back to you and thank you very much for the GitHub Sponsor! It means a lot. 405 usually means that the HTTP status code is wrong - the |
Hello, No problem for the delay :-) It's an open source package I've tried this already in postman to make sure the API is not using another HTTP request The result is a correct json {"error":"invalid_client"} . This is also available in the API doc: https://documentation.acc.connect.easypost.eu/static/index.html Somehow it's not working with the request i'm doing with saloon. |
I've tried the new ->debug() with no luck... |
@labomatik Hi! Have you tried wrapping the Would it also be possible to get some more of the Connector code, as well as a full stack trace? |
This is the trace:
And the connector:
|
Hmm. Very odd. I can't really see anything wrong. I'm currently on my phone, but can test some stuff a bit later today. 🙂 |
Oh yes! removing the header did the trick, strange that the json is causing a 405 MethodNotAllowedException ... |
Very strange! I guess you could create a custom OAuth Request that uses the expected headers. I don't remember off the top of my head, but if the OAuth specification (or at least Client Credentials Grant) states that form data has to be used, then Saloon could enforce it. |
Hello,
I'm trying to implement a new API connection using OAuth2 but i'm facing a 405 error when trying to get the access token.
The counter part of the API is correctly sending the data:
The code is the following:
The connector is containing the defaultOauthConfig
The error thrown:
Do you have any idea why the result is 405?
The text was updated successfully, but these errors were encountered: