{"issue":{"created_at":"2011-11-21T08:23:20Z","state":"closed","updated_at":"2011-11-21T08:24:24Z","user":{"gravatar_id":"f710831c7c2fa4e8c717b25083f2a8b8","id":1027589,"url":"https://api.github.com/users/constantine27","login":"constantine27","avatar_url":"https://secure.gravatar.com/avatar/f710831c7c2fa4e8c717b25083f2a8b8?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"comments":1,"body":"You might get his message when you upgrade the previous version omniauth to the new 1.x one.\r\n\r\nNote that in the new version of omniauth-linkedin, linked_in is spelled as linkedin. Updating the changes in all your codes as well as database will solved the error message above.\r\n\r\nIn my case, I got the message when i try to find an existing user authentications record in which the provider is stored as linked_in(default for the previous version).\r\n\r\nThought I might save some time for the other developers.\r\n\r\nGood work skorks. thank you.","assignee":null,"id":2302420,"number":4,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"labels":[],"title":"Error authenticating /auth/failure?message=invalid_response","closed_at":"2011-11-21T08:24:24Z","html_url":"https://github.com/skorks/omniauth-linkedin/issues/4","milestone":null,"url":"https://api.github.com/repos/skorks/omniauth-linkedin/issues/4"},"action":"created","comment":{"created_at":"2011-11-21T08:24:24Z","updated_at":"2011-11-21T08:24:24Z","user":{"gravatar_id":"f710831c7c2fa4e8c717b25083f2a8b8","id":1027589,"url":"https://api.github.com/users/constantine27","login":"constantine27","avatar_url":"https://secure.gravatar.com/avatar/f710831c7c2fa4e8c717b25083f2a8b8?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"body":"Not an issue so im closing it.","id":2812508,"url":"https://api.github.com/repos/skorks/omniauth-linkedin/issues/comments/2812508"}}