You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had issues with getting the token. I noticed that Ruby client works fine. Then I investigated there requests and found out that the Ruby client send also the client_secret on the wire.
Although this can be accomplished by appending this param again to the get token request client = OAuth2.Client.get_token!(client, code: "xxxxxxxxx", client_secret: "xxxxxxx")
this is not at all obvious and neither documented in the readme. I lost a few days debugging this issue.
I suggest that OAuth2.Strategy.AuthCode to do this by itself. Can I make a pull request with this?
The text was updated successfully, but these errors were encountered:
@silviurosu I'm sorry to hear of your troubles. You're not the only one who has run into something like this. This issue has come up a few times before.
The problem is, this library attempts to provide strategies that follow the OAuth2 specification but allow for users to extend them, OR write a specific strategy for the target service.
I probably won't accept a PR that adds client_secret to the AuthCode strategy, but I will gladly accept a PR that outlines this issue in the README.
I had issues with getting the token. I noticed that Ruby client works fine. Then I investigated there requests and found out that the Ruby client send also the client_secret on the wire.
Although this can be accomplished by appending this param again to the get token request
client = OAuth2.Client.get_token!(client, code: "xxxxxxxxx", client_secret: "xxxxxxx")
this is not at all obvious and neither documented in the readme. I lost a few days debugging this issue.
I suggest that
OAuth2.Strategy.AuthCode
to do this by itself. Can I make a pull request with this?The text was updated successfully, but these errors were encountered: