Devise Oauth Twitter: OAuth::Unauthorized Forbidden 403

Question

I am trying to implement Oauth Twitter using Devise.
I have created app on twitter
I have set callback url to: http://localhost:3000
I have added this to config\\initializers\\devise.rb

  config.omniauth :twitter, "key", "key secret"

Sign in with Twitter automatically appears at this route: /users/sign_up/ But on clicking it I get this error

key and key secret are correct

I also tried deleting and creating new app.

I cannot get it fixed

Help would be greatly appreciated

Here it says that https needs to be setup. So I followed This to set it up. But getting the same error

Answer 1

Turns out that in twitter app settings Callback URL Lock was set to Yes by default. Switching it to No fixed the error.

Thanks to kubido for helping me out to close the issue on github

Answer 2

You can try to add these in the Callback URLs in https://apps.twitter.com/

• http://localhost:3000/auth/twitter/callback
• http://127.0.0.1:3000/
• http://127.0.0.1:3000/auth/twitter/callback

Worked for me after almost an hour!

I got these URLs after failing the log-in. I checked the request_options. One way to do it is using BetterErrors gem.

Answer 3

I had been facing the same issue, eventually i fixed it by adding the following callbacks,

http://127.0.0.1:3000/auth/twitter/callback
http://127.0.0.1/
http://127.0.0.1/auth/twitter/callback
http://localhost:3000/auth/twitter/callback

and it worked like a charm,

Answer 4

您需要将回调网址设置为：“您的网址”/auth/twitter/callback

Answer 5

I am trying to implement Oauth Twitter using Devise.
I have created app on twitter
I have set callback url to: http://localhost:3000
I have added this to config\\initializers\\devise.rb

  config.omniauth :twitter, "key", "key secret"

Sign in with Twitter automatically appears at this route: /users/sign_up/ But on clicking it I get this error

key and key secret are correct

I also tried deleting and creating new app.

I cannot get it fixed

Help would be greatly appreciated

Here it says that https needs to be setup. So I followed This to set it up. But getting the same error