LinkedIn oauth fails at getting a request token

[Willooz]

Hi, I'm getting the following response from LinkedIn Oauth:
{"error_description":"missing required parameters, includes an invalid parameter value, parameter more than once. : Unable to retrieve access token : appId or redirect uri does not match authorization code or authorization code expired","error":"invalid_request"}

The problem seems to happen at Step 3 — Exchange Authorization Code for a Request Token (https://developer.linkedin.com/docs/oauth2).

When I look at the request made by omniauth (lib/oauth2/client.rb)...

{:raise_errors=>true, :parse=>nil, :body=>{"grant_type"=>"authorization_code", "code"=>"AQRXa3pON-Dz2PeQiHesH0k0ENLI1M_NdcUY2Y5Gae7EpiRnBrwLcEBHqF5E9opvNqtqP5kRaXXweTJwyp8oJfv5yXEMUlotjuMTt2L80D6mTp8-cGw", "client_id"=>"XXX", "client_secret"=>"XXX", :redirect_uri=>"http://localhost:3000/auth/linkedin/callback?code=AQRXa3pON-Dz2PeQiHesH0k0ENLI1M_NdcUY2Y5Gae7EpiRnBrwLcEBHqF5E9opvNqtqP5kRaXXweTJwyp8oJfv5yXEMUlotjuMTt2L80D6mTp8-cGw&state=16ae401bac5b0c55eba2089cd964a9590d587e81545a226f"}, :headers=>{"Content-Type"=>"application/x-www-form-urlencoded"}}

...and compare with LinkedIn requirements for Step 3, the only difference I see is the redirect_uri encoding.

Could that be the problem? Can it be fixed? Has anyone else had that type of issue?

Thanks for helping!

[zmajstor]

you can try with quick fix in Gemfile: gem 'omniauth-oauth2', '1.3.1' if the problem is the same as here:
omniauth/omniauth#825 (comment)

[igrabes]

This worked for me. Thanks

[Willooz]

It worked, thank you so much! 👍

[cristianogregnanin]

this work for me

[raouldevil]

This issue is still unresolved, encountered today, solved with @zmajstor fix. A long term solution would be great.

[colinexl]

this worked for me as well

[kumaresan-rails]

Was this issue resolved.? I am still facing the issue even after using gem 'omniauth-oauth2', '1.3.1.

[ashadev]

@kumaresan-rails Were you able to solve this issue? I'm facing the same even after using omniauth-oauth2 1.3.1.

[SoorajChandran]

Facing the same issue. Any solutions ?

[alexandru-calinoiu]

Looks like the issue is fixed on a commit on master 80f5f73