Nativefier: Can't login with google oauth

Created on 22 Dec 2018 · 6Comments · Source: jiahaog/nativefier

Description

I can't log in to a created application with as a google user

Steps to reproduce issue

1) Make an app from the pomodoro tracker site
2) Try to log in as a google user; the app will transfer me to the actual chrome at this step; if I select my account - it will show error 403: Invalid token "".; meanwhile the created application doesn't respond

Details

Are you nativefying a public website? - Yes
Feature request? Have you looked at nativefier --help to see if an existing option could fit your needs? - Not applicable
Full nativefier command used to build your app: nativefier https://pomodoro-tracker.com/
Version of Nativefier (run nativefier --version): v7.6.9
Version of node.js (run node --version): v11.4.0
OS: Mac OS 10.14.2
Error message / stack trace (if any):

403: Invalid token "".

Source

Hatko

👍1

Most helpful comment

For me just adding the main domain again to the internal urls (in addition to the Google authentication domain accounts.google.com) did the trick.

Example for https://next.focuster.com which uses Google OAuth for login:

nativefier --name "Focuster" "https://next.focuster.com" --internal-urls "accounts.google.com|next.focuster.com"

Note: it will not always be the main domain, that you need to add to internal URLs. If it doesn't work:

Pull up developer tools in your browser
Make sure to "preserve logs" in the network tab (see https://stackoverflow.com/a/12282621/304266)
Run through the auth flow in your browser
Add all domains in the flow (including redirects, that's why we initially chose to preserve the logs) into internal URLs. Domain changes are highlighted in blue in the request list.

That should work for most auth implementations.

ubuntudroid on 5 Feb 2019

👍9 🎉4 ❤3

All 6 comments

A similar issue is with To do from microsoft. If you try to sign in - it will just show loading and redirect you to the browser

Hatko on 23 Dec 2018

👍2

Similar issue at #745.

jebeld17 on 22 Jan 2019

For me just adding the main domain again to the internal urls (in addition to the Google authentication domain accounts.google.com) did the trick.

Example for https://next.focuster.com which uses Google OAuth for login:

nativefier --name "Focuster" "https://next.focuster.com" --internal-urls "accounts.google.com|next.focuster.com"

Note: it will not always be the main domain, that you need to add to internal URLs. If it doesn't work:

Pull up developer tools in your browser
Make sure to "preserve logs" in the network tab (see https://stackoverflow.com/a/12282621/304266)
Run through the auth flow in your browser
Add all domains in the flow (including redirects, that's why we initially chose to preserve the logs) into internal URLs. Domain changes are highlighted in blue in the request list.

That should work for most auth implementations.

ubuntudroid on 5 Feb 2019

👍9 🎉4 ❤3

Thank you @ubuntudroid, this solution saved me.

For anyone trying to add Jira (without access to a Jira account with Google login) a slightly modified version of the code above worked for me:

nativefier --name "Jira" "https://safetysync.atlassian.net" --internal-urls "id.atlassian.com/login|safetysync.atlassian.net"

This will let you login with email/password without booting you to a browser window which displays an error.

danielkuhlwein on 9 May 2019

👍5 ❤1

If you're authentication using Microsoft AD then you need to add login.microsoftonline.com to internal urls.

disklosr on 14 Jun 2019

Looks like --internal-urls is doing the trick. Closing to centralize discussion around https://github.com/jiahaog/nativefier/issues/706#issuecomment-602057644 , PR welcome.