omniauth

In Railscast: http://railscasts.com/episodes/241-simple-omniauth Ryan uses omniauth for logins. In the video when he clicks on the login button the first time Twitter asks the user if they would like to authorize Ryan's app. The second time the login button is clicked it automatically logs the user in. In my application, the user is forced to authorize my app each time. If the user is logged into twitter and has already authorized the app, then shouldn't it "just work"? EDIT: my app currently has Read, write, and direct message permissions. I'm also using omniauth-twitter (0.0.6). arunagw Ok

After having watched Ryan's excellent Railcast Simple OmniAuth , I've managed to implement authentication in my app. Everything is working fine, but in my view I have links that look like this: <%= link_to 'Sign in with Twitter', '/signin/twitter' %> <%= link_to 'Sign in with Facebook', '/signin/facebook' %> I was wondering if there is an elegant way to create a named route to replace that with: <%= link_to 'Sign in with Twitter', signin_twitter_path %> <%= link_to 'Sign in with Facebook', signin_facebook_path %> or: <%= link_to 'Sign in with Twitter', signin_path(:twitter) %> <%= link_to

I've seen many answers here, but none of them has worked. I'm using omniauth-oauth2 gem to integrate with a third-party customer. I'm using the setup phase described here but I'm always getting this error: Authentication failure! failed_to_connect: Faraday::Error::ConnectionFailed, SSL_connect SYSCALL returned=5 errno=0 state=SSLv2/v3 read server hello A Faraday::Error::ConnectionFailed (SSL_connect SYSCALL returned=5 errno=0 state=SSLv2/v3 read server hello A): .rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/net/http.rb:918:in `connect' .rvm/rubies/ruby-2.0.0-p247/lib/ruby/2.0.0/net/http.rb:918:in

Hi I am learning how to use omniauth as backend for ember app. when i run my application I get the below mentioned erroe OmniAuth::NoSessionError - You must provide a session to use OmniAuth on resue rails s my applicataion halts at line below. 172: def call!(env) # rubocop:disable CyclomaticComplexity 173: unless env['rack.session'] 174: error = OmniAuth::NoSessionError.new('You must provide a session to use OmniAuth.') => 175: fail(error) 176: end 177: config/intializer/devise Devise.setup do |config| config.mailer_sender = 'please-change-me-at-config-initializers-devise@example.com' require

I am using OmniAuth to get access to Facebook in my app. I am using the fb_graph gem: https://github.com/nov/fb_graph to post to Facebook. I am running omniauth-0.3.0 on Heroku for this app. The token that I save when the user is created is changed when the user logs in sometime later. Code for creating user class SessionsController < ApplicationController def create auth = request.env["omniauth.auth"] user = User.find_by_provider_and_uid(auth["provider"], auth["uid"])|| User.create_with_omniauth(auth) session[:user_id] = user.id redirect_to root_url, :notice => "Signed in!" end The User model

The URL's seem right (Last updated them yesterday): The files too: omniauth.rb: provider :google_oauth2, 'MY_CLIENT_ID.apps.googleusercontent.com', 'MY_CLIENT_SECRET', :scope => 'https://mail.google.com/mail/feed/atom/' Error: redirect_uri_mismatch The redirect URI in the request: http://localhost:3000/auth/google_oauth2/callback did not match a registered redirect URI header.html.erb <li><%= link_to "Sign in with Google", "auth/google_oauth2" %></li> routes.rb: match '/auth/:provider/callback', to: 'sessions#omniauth_create' But I'm getting this: > Error: redirect_uri_mismatch The redirect

So I have been pulling my hair out for a few days now trying to figure out how to add username/password authentication to my rails mobile API. Here is a brief overview of my current authentication flow: User selects "login with Facebook" on the mobile client, client redirects to Facebook app and requests access_token On success, Facebook responds with the access token and the client redirects back to my app. The client sends the access token to my API My API uses the koala gem to check if the access token is valid. If the token is valid, Facebook sends the users data to the API where a new