Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for Google provided email accounts (i.e. [email protected]) #350

Closed
TinfoilSubmarine opened this issue Jul 24, 2017 · 22 comments
Closed

Comments

@TinfoilSubmarine
Copy link

I'm attempting to login with my Google-provided account. The domain-name part of the address is not gmail.com but rather my organization's domain name. Is there support for this and I'm just missing something?

@tdryer
Copy link
Owner

tdryer commented Aug 7, 2017

That should work as long as your organization is using the standard Google login form.

@TinfoilSubmarine
Copy link
Author

And if they do not use the standard Google login form? Is it completely out of the question?

@tdryer
Copy link
Owner

tdryer commented Aug 18, 2017

You're out of luck then, although it's possible to log in manually using a web browser. I can document the steps for that if you're still interested.

@TinfoilSubmarine
Copy link
Author

I would be willing to try that. Thanks in advance.

@tdryer
Copy link
Owner

tdryer commented Aug 19, 2017

Manual login process:

  1. Download and run this Python script. It requires hangups to be installed.
  2. Open the URL provided by the script in your browser.
  3. If prompted, log into your Google account normally.
  4. You should be redirected to a page that says "One moment please...". Copy the oauth_code cookie value set by this page (instructions below for Chrome):
    1. Press F12 to open DevTools.
    2. Select the "Application" tab.
    3. In the sidebar, expand "Cookies" and select https://accounts.google.com.
    4. In the cookie list, double click on the value for the oauth_code cookie to select it, and copy the value.
  5. Paste the value back into the script's prompt and press enter.

EDIT: You can now specify --manual-login to do the same thing through hangups.

@TinfoilSubmarine
Copy link
Author

Worked like a charm. Thanks again!

@mstfacmly
Copy link

I tried running the script. It tells me that it can't find the hangups module, even though I can run hangups.

@das7pad
Copy link
Contributor

das7pad commented Nov 7, 2017

@MoustafaC Could you try it again with a virtual environment?

python3 -m venv ~/venv
~/venv/bin/pip3 install hangups
~/venv/bin/python3 /path/to/the/gist/script

@mstfacmly
Copy link

Sorry for the delay. Tried it in a virtual environment, and it works.

Thanks!

@colton22
Copy link

colton22 commented May 25, 2018

Thank you for this! @tdryer

@rustbuckett
Copy link

Totally worked. Easy peasy.

@lanmower
Copy link

As far as I can tell this doesn't work any more.

image
this just shows for ever and ever.

@colton22
Copy link

@lanmower it does show that. Read the rest of the direction, you need to extract data from a cookie in the browser. Step 4.

@zetorian
Copy link

I had a similar issue, which the given script resolves.

as this becomes a more common issue, would it make sense to include the above script as a part of the default hangups package, perhaps used by a flag i.e. (hangups --manual-login) with slightly better print statements to guide users through in case normal login doesn't work?

@colton22
Copy link

Or a link to this repo in the program...

@lanmower
Copy link

lanmower commented Oct 25, 2018

I second @zetorian I think updating the code is a better solution than using workarounds :)

P.S. thanx for the help, I am successfully using hangups and although its janky it works when in place, very happy that I can cli out hangouts messages now, which also required a second script/workaorund, which I had to fix myself cause it was out of date etc etc...

@zetorian
Copy link

working on a pull request I should be able to publish this weekend which would add a flag --manual-login to trigger the script

@tdryer
Copy link
Owner

tdryer commented Nov 1, 2018

We might be stuck with the manual login method soon. Google says their login form is going to require JavaScript:

When your username and password are entered on Google’s sign-in page, we’ll run a risk assessment and only allow the sign-in if nothing looks suspicious. We’re always working to improve this analysis, and we’ll now require that JavaScript is enabled on the Google sign-in page, without which we can’t run this assessment.

@eddyizm
Copy link

eddyizm commented Nov 9, 2018

Do we need to run this work around every time we want to fire up hangups from CLI ?

@Terrance
Copy link
Contributor

Terrance commented Nov 9, 2018

Only for the initial login -- after that you'll have a text file containing your authentication cookie, which doesn't require going through Google's auth flow to use.

@tdryer
Copy link
Owner

tdryer commented Nov 12, 2018

--manual-login is now available as suggested by @zetorian.

@paxperscientiam
Copy link

@tdryer , wow, i finally got it to work! For anyone else using FF, do this after opening dev tools:
screenshot 2019-02-03 15 46 52

@tdryer tdryer mentioned this issue May 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests