Org Web Adapter

pages/eng_11071_fix_google_social_auth_login_token_id_issue.org

ID
df0307cb-0a67-41da-a1c8-4d5943a136bc
ROAM_ALIASES
ENG-11071

ENG-11071 - Fix Google+ social auth login token_id issue

- tags :: Jira 15Five

- source :: https://15five-dev.atlassian.net/browse/ENG-11071

Description

Original quip doc: https://15five.quip.com/i8OEALbGvlEg

Currently we are using `access_token` parameter in login google+ API - which is deprecated as of now and we are using deprecated google+ library to get this token.

We would like to switch to latest google library that is giving `id_token` instead

πŸ† Desired Outcome from problem #19

We will know we've been successful when:

API login_with_access_token/google-plus will support `token_id` parameter to be able to sign in user via google+

πŸ“… Due Date: Q4 2020 - Q1 2021

βœ… Priority: Medium-High

Notes

- Note taken on

This is likely resolve by https://github.com/python-social-auth/social-core/issues/401

Unfortunately, that fix is not in any release yet. Steps to take are to test that solution to make sure it works for us and if it does, open a PR against python-social-auth with a 15Five fork that we can use to manage our deps until the PR is merged and a release is cut.