The Google provider is OAuth2 based.

More info:

App registration

Create a google app to obtain a key and secret through the developer console.

Google Developer Console

After you create a project you will have to create a “Client ID” and fill in some project details for the consent form that will be presented to the client.

Under “APIs & auth” go to “Credentials” and create a new Client ID. Probably you will want a “Web application” Client ID. Provide your domain name or test domain name in “Authorized JavaScript origins”. Finally fill in in the “Authorized redirect URI” field. You can fill multiple URLs, one for each test domain. After creating the Client ID you will find all details for the Django configuration on this page.

Users that login using the app will be presented a consent form. For this to work additional information is required. Under “APIs & auth” go to “Consent screen” and at least provide an email and product name.

Django configuration

The app credentials are configured for your Django installation via the admin interface. Create a new socialapp through /admin/socialaccount/socialapp/.

Fill in the form as follows:

  • Provider, “Google”

  • Name, your pick, suggest “Google”

  • Client id, is called “Client ID” by Google

  • Secret key, is called “Client secret” by Google

  • Key, is not needed, leave blank.

Optionally, you can specify the scope to use as follows:

    'google': {
        'SCOPE': [
        'AUTH_PARAMS': {
            'access_type': 'online',
        'OAUTH_PKCE_ENABLED': True,

By default (if you do not specify SCOPE), profile scope is requested, and optionally email scope depending on whether or not SOCIALACCOUNT_QUERY_EMAIL is enabled.

You must set AUTH_PARAMS['access_type'] to offline in order to receive a refresh token on first login and on reauthentication requests (which is needed to refresh authentication tokens in the background, without involving the user’s browser). When unspecified, Google defaults to online.

By default, the userinfo endpoint will not be fetched. In most cases, this will be fine, as most in scope user data is gained via decoding the JWT. However if users have a private style of avatar_url then this will not ordinarily be returned in the JWT and as such, subsequent calls to get_avatar_url will return None.

You can optionally specify the following setting so that the userinfo endpoint will be used to populate the avatar_url for those users who have a private style of avatar_url.

    'google': {
        'FETCH_USERINFO' : True

One Tap Sign-In

One Tap Sign-In can be enabled by adding a snippet like this snippet to your template:

<script src="//" async></script>
<div id="g_id_onload"
     data-login_uri="{% url 'google_login_by_token' %}"

Follow the Sign In with Google for Web guide for more information.