Coverage decreased (-12.2%) to 87.828% when pulling 6d49f4fd295efacaffde9c477c886976ae9f7a2d on freework-gmbh:master into ceb63460b8b45b7e00766ae3a4c3e361d76c6ffc on emorikawa:master.
Coverage decreased (-12.5%) to 87.453% when pulling 8025beabffadd6d69c265a839d805ad37e75b16b on freework-gmbh:master into ceb63460b8b45b7e00766ae3a4c3e361d76c6ffc on emorikawa:master.
Coverage decreased (-12.2%) to 87.828% when pulling 9f9a48b36208e11481cc368b5ceca51b8178f27d on freework-gmbh:master into ceb63460b8b45b7e00766ae3a4c3e361d76c6ffc on emorikawa:master.
Coverage decreased (-12.2%) to 87.828% when pulling 876206861d5005a2a654530f3888b1a4d121ecb8 on freework-gmbh:master into ceb63460b8b45b7e00766ae3a4c3e361d76c6ffc on emorikawa:master.
Sending access token in query param returns status 401 for me.
https://stackoverflow.com/questions/31751441/linkedin-verify-oauth2-access-token-on-server-sidehttps://stackoverflow.com/questions/28094926/linkedin-oauth2-unable-to-verify-access-token
Sending in header works for me. Note: I am using an access token acquired from mobile SDK