Changes between Initial Version and Version 2 of Ticket #33846


Ignore:
Timestamp:
Jul 18, 2022, 10:21:35 AM (2 years ago)
Author:
Clark
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #33846

    • Property Resolution → invalid
    • Property Status new → closed

  • Ticket #33846 – Description

    initial v2  
     1Hello everyone,
     2I'm having difficulty using Django 4.0 with Google OAuth2.0 SDK.
     3And I wrote down the specific way to reproduce the problem because this is a bit tricky issue to explain with words.
     4Please leave a comment, if you have any questions.
    15
    2 ''TL;DR''
     6\\
     7
     8''TL;DR
    39Django 4.x and Google OAuth2.0 SDK(new way) conflict for some reasons.
    4 Anyone who is using Google OAuth2.0 SDK with Django 4x?
     10Anyone who is using Google OAuth2.0 SDK with Django 4x?''
    511
    612
    … …  
    144150\\
    145151
    146 On a side note, I served this Google SDK code with "webpack-dev-server"(https://github.com/webpack/webpack-dev-server) without using Django rendering, and it works fine.
     152On a side note, I compared the request and response from Google Auth Server between Django 3.x and 4.x. and there was no difference.
     153So, I think Google Auth Server has no problem with regard to this issue but Google Client library(https://accounts.google.com/gsi/client) served by Django does have an issue.
     154
     155(Response from Google Auth Server on Django 3.2.14)
     156{{{
     157[[["gf.sisr",6,null,null,null,null,null,["gf.cr",4,null,null,[4,null,null,null,["{\n  \"access_token\" : \"ya29.A0AVA9y1sCNWa5H1iHI3Ebjjo4OGX551lV1...63\",\n  \"token_type\" : \"Bearer\",\n  \"expires_in\" : 3598,\n  \"scope\" : \"email profile openid https://www.googleapis.com/auth/calendar.readonly https://www.googleapis.com/auth/userinfo.profile https://www.googleapis.com/auth/contacts.readonly https://www.googleapis.com/auth/userinfo.email\",\n  \"authuser\" : \"0\",\n  \"hd\" : \"test.com\",\n  \"prompt\" : \"none\"\n}","753749545716-dg8sl....apps.googleusercontent.com","auth712297","http://localhost:8000",null,1]],null,null,[]]],["gf.ttu",1],["e",3,null,null,891]]]
     158}}}
     159
     160(Response from Google Auth Server on Django 4.0.6)
     161{{{
     162[[["gf.sisr",6,null,null,null,null,null,["gf.cr",4,null,null,[4,null,null,null,["{\n  \"access_token\" : \"ya29.A0AVA9y1viWoIqts1eK57kJEEOXKK2NJrW86O99FPmmLRabPVkceigfo5B5xa-RDfIuEdymAyJz52I4udUU...Wp1ZHI4a19BY0t3MDVZQ3U0UEhkeUdHVDBLUQ0163\",\n  \"token_type\" : \"Bearer\",\n  \"expires_in\" : 3599,\n  \"scope\" : \"email profile https://www.googleapis.com/auth/calendar.readonly https://www.googleapis.com/auth/userinfo.profile https://www.googleapis.com/auth/userinfo.email openid https://www.googleapis.com/auth/contacts.readonly\",\n  \"authuser\" : \"0\",\n  \"hd\" : \"test.com\",\n  \"prompt\" : \"none\"\n}","753749545716-dg....apps.googleusercontent.com","auth717087","http://localhost:8000",null,1]],null,null,[]]],["gf.ttu",1],["e",3,null,null,891]]
     163}}}
     164
     165\\
     166
     167Plus, I tried testing this Google SDK code with "webpack-dev-server"([https://github.com/webpack/webpack-dev-server](https://github.com/webpack/webpack-dev-server)) without using Django rendering, and it works fine.
    147168That's why I suspect that the updated Django rendering code in v4.0 is the cause of the problem.
    148169
    149 
    150 Plus, I compared the request and response from Google Auth Server between Django 3.x and 4.x. and there was no difference.
    151 So, I think Google Auth Server has no problem with regard to this issue but Google Client library(https://accounts.google.com/gsi/client) served by Django does have an issue.
    152 
    153 
Back to Top