Not Supported notice

Created on 20 March 2024, 8 months ago
Updated 1 June 2024, 6 months ago

Message on available updates page:

Project not supported: This project is no longer supported, and is no longer available for download. Disabling everything included by this project is strongly recommended!

We are definitely still successfully using this module and would like to continue using it. Please inform if we should move off of it.

Thanks for the great work!

💬 Support request
Status

Active

Version

3.0

Component

Code

Created by

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @danstorm
  • Does Social Auth Google API register a user? Do you know, if that module uses ID Token (Google) or uniquely Access Token? I tried ID Token and it seems that it doesn't work. Is there a way to get an Access Token on Android by using Credential Manager, do you know? It would be helpful to know how that module works.

  • 🇨🇳China lawxen

    We are seeking new maintainers, I haven't use Social Auth* relevant module for a long time
    You can see the code directly, This is a small module with very little code

  • OK, I needed authenticateNewUser by the info from social account (Google account). I used those both modules (including social_auth_google_api). It seemed that the json link worked (in the browser it was recognised) but when I sent a Google ID Token by using /user/login/google?_format=json` [POST], there was an error. I used Social API v3, Social Auth v3 and Social Auth Google v3 to have them as compatible as possible but Drupal 10 (I changed the modules to have drupal 10 in their files).

    If you used those modules for Drupal 8/9, could you confirm or disprove that social_auth_google_api worked with Google ID Token or it worked uniquely with Google Access Tokens? For the last case I suppose that either it's not safe to use client_id on Android app or it worked with already registered accounts on Drupal, so it's only for authenticateExistingUser, not for authenticateNewUser? Is my logic correct or not?

  • It won't work. For example, there's "drupal/social_auth": "^3.0" in composer.json (3.0 version only works with drupal 9).

Production build 0.71.5 2024