Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

request.jar breaks linkedIn's oAuth2 flow #494

MikeLindenau opened this Issue Mar 29, 2013 · 1 comment


None yet
2 participants

Just a heads up. With request.jar set to true (which is default) I could not complete linkedin's oAuth2 flow. Everything worked fine until I sent a request to the api after receiving a users authorization.

I guess linkedIn set the cookie when the user authorizes the app:

leo_auth_token="GST:8g9dFmC06EEeQmi4M- 9fFmm_J779E1amHEULfLM6xsEsTmb46_sy4s:1364515371:463a8c904e50f8be059fd99b12dd443b373695bb"

When making an api request it seems to send this cookie with it which couse an exception:

{"id":{"errorCode":0,"message":"[invalid.auth.token.type]. Authentication token type {GST} is not valid here.","requestId":"6XYP7FPIGR","status":401,"timestamp":1364501128399}}

The fix: set request.jar to false.

An explanation would be cool as I dont quite get why its doing that


mikeal commented Aug 27, 2014

Is this still an issue?

This is so old I'm closing, if it is actually still an issue just let me know and I'll re-open.

@mikeal mikeal closed this Aug 27, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment