Omniauth-linkedin parameter_absent error.

[shaileshgupta]

My omniauth configurations look like:

Rails.application.config.middleware.use OmniAuth::Builder do provider :linkedin, ENV["linkedin_key"], ENV["linkedin_secret"] provider :identity, on_failed_registration: lambda { |env| SessionsController.action(:new).call(env) } end

I have rechecked my key / secret value and it matches that given in the app_key section given on LinkedIn. However, today, I suddenly started getting following error:

Started GET "/auth/linkedin/callback?oauth_token=0fd17840-7b0c-4603-aa73-bf2eacf60510&oauth_verifier=29377" for 127.0.0.1 at 2013-08-04 13:55:09 +0530 (linkedin) Callback phase initiated. (linkedin) Authentication failure! invalid_credentials: OAuth::Problem, parameter_absent Processing by SessionsController#oauth_failure as HTML Parameters: {"oauth_token"=>"0fd17840-7b0c-4603-aa73-bf2eacf60510", "oauth_verifier"=>"29377"} Rendered sessions/oauth_failure.html.erb within layouts/application (0.2ms) Rendered layouts/_header.html.erb (0.2ms) Rendered layouts/_footer.html.erb (0.2ms)

Can you please suggest where I may be doing something wrong or if the issue with the gem.

[ronhornbaker]

I'm seeing a possibly related new problem that just started today. The auth hash returned by omniauth-linkedin has a credentials.token, but no credentials.secret, so I can no longer use the linkedin-oauth gem for further api hits. Perhaps LinkedIn is having issues?

[rtcoms]

I am also facing same issue . Any update on this ?

[LaurMo]

We're facing the same issue and I've opened a Stackoverflow post here. @shaileshgupta, @ronhornbaker, @rtcoms did you find a way around the issue?