2011-06-01, 15:16
stout Wrote:Adding this in because I have been in the situation before where I'll spend a month troubleshooting something and constantly finding people asking the same questions I do, but never finding an answer....
With 2factor authentication enabled, I successfully set up an application specific password (google makes it easy for you to find help n how to do this - if you were smart enough to setup 2fact auth, you'll find where to add app specific passwords) and got the youtube plugin working with that.
Awesome sauce.
Updating the plugin to OAuth is still not a bad idea, though. ClientLogin is recognized by google as being buggy, prone to problems, and deprecated.
Hi,
from my own testing using application specific passwords break the scraper part of the plugin (YouTube recommendes and so forth) since google has banned those from its web login (at-least they had last time i checked)
We had recently gone over this and dismissed using oauth 2 due to the problems we perceived this would give 2 factor authentication user, but those seem to be workable at-least.
The switch to Oauth would still not alleviate the central privacy issues that users might have, as we would need to script the entire process like we do with the vimeo login (Not all platforms have a web browser available, and even if they did navigating a web browser with your remote is a nightmare).
The plugins login issues are in my experience limited to ssl problems with the python distribution that xbmc includes on windows, on osx and ubuntu these problems are non-existent. That being said I'll look into oauth 2, but it's gonna require a major reworking of the current login code.