Note that there are some explanatory texts on larger screens.

plurals
  1. POHow do I authenticate users in a Rails app with the oauth gem and twitter 1.0.0 gem?
    text
    copied!<p>Jnunemaker just updated his twitter gem (https://github.com/jnunemaker/twitter) and removed the Twitter::Oauth class. My code doesn't look much like his example, so I'm having issues updating it. Here's what my code used to look with the twitter 0.9 gem:</p> <h1>UsersController</h1> <pre><code>def oauth consumer = Twitter::OAuth.new('mykey','mysecret') request_token = consumer.request_token session[:request_token] = request_token.token session[:request_token_secret] = request_token.secret redirect_to 'http://api.twitter.com/oauth/authorize?oauth_token='+request_token.token end def callback consumer = Twitter::OAuth.new('mykey','mysecret') atoken, asecret = oauth.authorize_from_request(session[:request_token], session[:request_token_secret], params[:oauth_verifier]) consumer.authorize_from_access(atoken,asecret) user = Twitter::Base.new(consumer).verify_credentials #and then I create a new user in my application, with attributes such as the user's follower count, etc end </code></pre> <p>Here's an example of what I've tried to do to change this code:</p> <h1>UsersController</h1> <pre><code>def oauth consumer = OAuth::Consumer.new("mykey", "mysecret", :site =&gt; "siteurl") request_token = consumer.get_request_token session[:request_token] = request_token.token session[:request_token_secret] = request_token.secret redirect_to 'http://api.twitter.com/oauth/authorize?oauth_token='+request_token.token end def callback consumer = OAuth::Consumer.new("mykey", "mysecret", :site =&gt; "siteurl") request_token = session[:request_token] atoken = OAuth::RequestToken.new(consumer, request_token.token, request_token.secret).get_access_token(:oauth_verifier =&gt; params[:oauth_verifier]) consumer.authorize_from_access(atoken) user = Twitter::Client.new(consumer).verify_credentials </code></pre> <h1>Gemfile</h1> <pre><code>... gem 'oauth' </code></pre> <p>I'm sure there are a number of things wrong in my callback method, but one thing that's weird is that my oauth method works fine when I'm running locally, but gives me a '502 Bad Gateway' error when I try from my live (deployed with heroku) version.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload