V8-archive: Google Auth stuck at Logging In ...

[RyanPrice-King]

Bug Report

Steps to Reproduce

Login Google Auth

Expected Behavior

Logs In successfully

Actual Behavior

Stuck "Signing In..."

Other Context & Screenshots

If I switch to Directus App 7.0.11 it immediately works until I switch to another version from 7.0.12 - 7.0.15, it doesn't log in and I get this issue again.

I can login manually with same username.

I cannot see anything added to API logs when this happens and I cannot find the docker APP logs to check them.

Technical Details

• Device: Desktop
• OS: Windows and Ubuntu
• Browser: [eg: Chrome 68.0.3440.106]
• Directus App: 7.0.15 (docker)
• Directus API: 2.0.15
• Install Method: Git clone seperate API and APP with Clean fresh install of DB

[rijkvanzanten]

Is there any error logged in the browser console?

[RyanPrice-King]

No. Nothing at all sorry.

[srjrol]

I am experiencing the same problem with Google SSO stuck signing in...
The same user account/email works with manual login.

Desktop
Google Chrome Version 72.0.3626.109 (Official Build) (64-bit)
Windows 10 Pro version 1809 OS build 17763.316
Directus v7.0.18 (combined released installed/updated by cPanel Git™ Version Control)

[RyanPrice-King]

Yes. If you drop the app and use the .11 app it works again.

On Tue, 19 Feb 2019, 18:44 srjrol <[email protected] wrote:

I am experiencing the same problem with Google SSO stuck signing in...
The same user account/email works with manual login.

Desktop
Google Chrome Version 72.0.3626.109 (Official Build) (64-bit)
Windows 10 Pro version 1809 OS build 17763.316
Directus v7.0.18 (combined released installed/updated by cPanel Git™
Version Control)

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/directus/app/issues/1275#issuecomment-465259093, or mute
the thread
https://github.com/notifications/unsubscribe-auth/Age3GvVL6TvduCcxkgPp8p9Zgj02p0bIks5vPEX5gaJpZM4aSv5F
.

[srjrol]

Yes. If you drop the app and use the .11 app it works again.
Thanks but unfortunately this is not an option for me because I am using the combined release with app/api together.

[RyanPrice-King]

OK that is fine. I use docker for the app and git clone for the API separately. So I am able to switch app versions easily. I guess just take my word then that this problem happens from app version .12 onwards. I hope this helps.

[scleriot]

I am experiencing the same problem, .11 works fine but latest version is stuck on "Logging in...". No error logged in the browser console

Desktop
Google Chrome Version 73.0.3683.75 (Build officiel) (64 bits)
Ubuntu

[fyip]

Have you guys managed to find a fix or work around for this?

[benhaynes]

Since the ticket's still open, my guess is there is not good fix/workaround yet. Ideally this is resolved in the next week or two though.

[bjgajjar]

Is seems like there's an issue in API which culprit for this issue. So transferring it to API.

[bjgajjar]

After analaysing the code; I able to find out that; Google Auth is working as expected.

• Generally, social login works as the role of FindOrCreate [Return the user if exists or create a new with those details] but here the functionality exists for Admin Panel and Admin cant register themselves.

• The social login works perfectly for those users who are already registered and don't want to login with email and password.

  • Let's assume there is an account with email [email protected] and one tried to login with the same google id. Then that user will able to login with google.
  • But if that user doesn't have an account in the system and tried to login with google then the system will redirect them to login page with exception that user is not exists in the system. Which is the expected behaviour. As Admin cant register themselves.

• The API return 107 code when user not found. So we just need to provide an alert or proper message at app side in this scenario.

Let me know your thoughts @rijkvanzanten

[theharshin]

Submitted a PR https://github.com/directus/app/pull/2022 which will display auth errors for SSO.

[bjgajjar]

As this issue is not reproducible in the latest version; I am closing this. Feel free to reopen it.