Skip to content
This repository has been archived by the owner on Sep 12, 2022. It is now read-only.

Improve Google auth flow #8

Closed
nblackburn opened this issue Sep 7, 2016 · 6 comments
Closed

Improve Google auth flow #8

nblackburn opened this issue Sep 7, 2016 · 6 comments

Comments

@nblackburn
Copy link

All other services create popups to sign in through official channels but Google works differently meaning it misses out on TOTP support and creating the impression of it being a second class citizen.

@vincelwt
Copy link
Owner

vincelwt commented Sep 7, 2016

Not sure if we can use an oauth based authentification as other services, as the API used for Google PM is unofficial.

Will look into it to see if it's possible

@aidanharris
Copy link

I found an old issue here. It seems the best way to use the playmusic library with a 2-factor enabled Google account is to create an app specific password.

Would it be possible to detect if an account has 2-factor enabled and provide a hint or perhaps open a webpage with instructions, so a user doesn't wonder "Why doesn't this work?" and give up on harmony.

@vincelwt
Copy link
Owner

vincelwt commented Sep 8, 2016

Thanks @aidanharris, I will add it to the README

@dwaq
Copy link

dwaq commented Sep 13, 2016

I think the method listed in the README "enable the insecure app access" is not the best route to go. I suggest linking users to the app password page, where they can create a specific password for the Harmony app.

I have tested and confirmed that this method works.

On a second look, the issue mentioned by @aidanharris mentions this method. I think the README just needs to be changed.

@vincelwt
Copy link
Owner

Added to the README :)

@vincelwt
Copy link
Owner

vincelwt commented Oct 9, 2016

I close this, as I don't think there is anything more doable with this current API.

@vincelwt vincelwt closed this as completed Oct 9, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants