{"action":"created","issue":{"url":"https://api.github.com/repos/NoamB/sorcery/issues/782","repository_url":"https://api.github.com/repos/NoamB/sorcery","labels_url":"https://api.github.com/repos/NoamB/sorcery/issues/782/labels{/name}","comments_url":"https://api.github.com/repos/NoamB/sorcery/issues/782/comments","events_url":"https://api.github.com/repos/NoamB/sorcery/issues/782/events","html_url":"https://github.com/NoamB/sorcery/issues/782","id":162525653,"number":782,"title":"Default initializer config for LinkedIn doesn't retrieve UID","user":{"login":"jeriko","id":273466,"avatar_url":"https://avatars.githubusercontent.com/u/273466?v=3","gravatar_id":"","url":"https://api.github.com/users/jeriko","html_url":"https://github.com/jeriko","followers_url":"https://api.github.com/users/jeriko/followers","following_url":"https://api.github.com/users/jeriko/following{/other_user}","gists_url":"https://api.github.com/users/jeriko/gists{/gist_id}","starred_url":"https://api.github.com/users/jeriko/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jeriko/subscriptions","organizations_url":"https://api.github.com/users/jeriko/orgs","repos_url":"https://api.github.com/users/jeriko/repos","events_url":"https://api.github.com/users/jeriko/events{/privacy}","received_events_url":"https://api.github.com/users/jeriko/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":12,"created_at":"2016-06-27T19:11:09Z","updated_at":"2016-07-21T23:02:50Z","closed_at":null,"body":"Not sure if something's recently changed with LinkedIn's API, but I had a bug in my app that traces back to `config.linkedin.user_info_fields = ['first-name', 'last-name']` in the initializer created by sorcery. During authentication, retrieving a `uid` fails since LinkedIn's response doesn't automatically include the field unless requested to.\r\n\r\nMy solution was simply `config.linkedin.user_info_fields << \"id\"`, but I think the generator should at least be updated to reflect working usage. Alternatively, perhaps the LinkedIn adapter should automatically include the id field in it's request, since several internal methods depend on its presence?"},"comment":{"url":"https://api.github.com/repos/NoamB/sorcery/issues/comments/234410106","html_url":"https://github.com/NoamB/sorcery/issues/782#issuecomment-234410106","issue_url":"https://api.github.com/repos/NoamB/sorcery/issues/782","id":234410106,"user":{"login":"Ch4s3","id":1943540,"avatar_url":"https://avatars.githubusercontent.com/u/1943540?v=3","gravatar_id":"","url":"https://api.github.com/users/Ch4s3","html_url":"https://github.com/Ch4s3","followers_url":"https://api.github.com/users/Ch4s3/followers","following_url":"https://api.github.com/users/Ch4s3/following{/other_user}","gists_url":"https://api.github.com/users/Ch4s3/gists{/gist_id}","starred_url":"https://api.github.com/users/Ch4s3/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Ch4s3/subscriptions","organizations_url":"https://api.github.com/users/Ch4s3/orgs","repos_url":"https://api.github.com/users/Ch4s3/repos","events_url":"https://api.github.com/users/Ch4s3/events{/privacy}","received_events_url":"https://api.github.com/users/Ch4s3/received_events","type":"User","site_admin":false},"created_at":"2016-07-21T23:02:50Z","updated_at":"2016-07-21T23:02:50Z","body":"I think it might be best to drop Oauth support in Sorcery 1.0 for Linkedin. But, I'm not 100% confident in that decision. Thoughts?"}}
{"actor":{"display_login":"Ch4s3"}}