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

AuthenticationError (BadAuthentication) in production environment with youtube new accounts #208

Open
hyperrjas opened this issue Feb 24, 2014 · 4 comments

Comments

@hyperrjas
Copy link

In my dev environment with localhost:3000 my new google plus username and password does works fine. I'm getting these data from google page settings:

screen

If you are using this new google plus settings, you must set up a new password from this page and use this password and this username in your youtube_it.yml file.

However when I try upload a video from my production domain I'm getting this error:

Completed 500 Internal Server Error in 263.8ms
AuthenticationError (BadAuthentication):

Thanks

@gnapse
Copy link

gnapse commented Oct 29, 2014

I'm getting AuthenticationError: BadAuthentication always. Just cloned the sample app, bundle install, rake db:migrate and rails s.

Whenever I try to upload a video, I get AuthenticationError: BadAuthentication. So I have to ask, although it seems to me like a silly question: what is the username and password that I have to put in the config/youtube_it.yml file? I assume it's something like:

common: &common
  dev_key: "my-developer-key"
  username:  "[email protected]"
  password:  "my-gmail-password"

Or is it something else?

@gnapse
Copy link

gnapse commented Nov 3, 2014

I found what was the problem. I have two-step authentication enabled on my google account, so the API client did not work with my regular password. I had to generate an app-specific password for it.

@jonasmora
Copy link

@gnapse did the api client work in dev with localhost:3000 even thought you had the two-step authentication?

I'm not sure about this, but I think that when the app tries to log in from production it's very likely that the server is in a different place than your computer and the sign-in is prevented by google.

https://security.google.com/settings/security/activity

@gnapse
Copy link

gnapse commented Jan 15, 2015

I don't know about production. I was using my own credentials just to test the app, on a development environment on localhost:3000. Probably on production it wouldn't work the same, but I never intended to use my own account with two-step auth in production.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants