-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LinkedIn OAuth2 bad request. #58
Comments
Actually switching the settings and the backend name should be enough, unless LinkedIn decided to break that migration option. Any luck on your end? |
funny enough the twitter dev discussion board had the answer for me...the callback URL in your linkedin app needs to be set -- even though it explicitly says oath1: this is what I did: |
@dblado, thanks for the clarification, I've added a reference in the docs regarding that. |
@omab What exactly do we need to specify in the redirect uri in the django app as well as the linkedin app? Add email to requested authorizations.SOCIAL_AUTH_LINKEDIN_OAUTH2_SCOPE = [ SOCIAL_AUTH_LOGIN_REDIRECT_URL = '/home/' Am I missing something in my config file, and exactly what should be the redirect uri in cas of OAuth2? |
I have a working django LinkedIn OAuth1 setup. I have tried to switch to OAuth2 by updating all my settings from SOCIAL_AUTH_LINKEDIN_* to SOCIAL_AUTH_LINKEDIN_OAUTH2_* and switching the backend to social.backends.linkedin.LinkedinOAuth2
I get an AuthCancelled Exception. Triggered I think by by HTTPError('400 Client Error: Bad Request',)
The inbound URL looks like:
http://bbm-dev.local:8000/complete/linkedin-oauth2/?redirect_state=c230xy4n04oSAG9x3xwcbEUgudTewZA1&code=AQShEKzGzz2n8lcfl7n9IxLwzWKs2R2g3kwFl5skR04z6Bk_LxYFQF3nrKSalI7Jk3mRGbFZAs60Csd2SW9yNwKZmPY39Iz7fx-E7T_2d2JIRvI7A-c&state=c230xy4n04oSAG9x3xwcbEUgudTewZA1
Have I missed anything in my setup changes? Any other ideas? Thanks.
The text was updated successfully, but these errors were encountered: