omniauth

问题 I'm working through the Railscast on implementing Devise and OmniAuth (along with the Devise documentation) -- currently, I've got a site going where visitors can sign up using their facebook accounts or by filling out a form. I'm running into trouble when users that sign up via OmniAuth try to edit their profiles, though. Devise looks for the user's current password when they submit changes to their profiles, but those that logged in with facebook don't know their passwords (they're set

问题 I'm using OmniAuth + Devise to allow users to register using Facebook/Twitter/Gowalla/etc attached to normal user accounts. Now when a user logs in using any of these, or their account, all their social networks are attached in a authentications table. I need to be able to pull content from any of these providers, such as their tweets or their Facebook Places checkings, etc. I understand that I will need to use a different gem, plugin, whatever to do this but getting the config I need to work

问题 I am new to Rails and am installing my first app that integrates Facebook sign in / sign up. I followed Ryan Bates' RailsCast videos that were posted here: https://stackoverflow.com/a/4954443/1302333. I followed his tutorial for integrating Twitter and that works, but I'm having issues with Facebook. When I visit http://localhost:3000/auth/facebook I receive this error: NoMethodError in AuthenticationsController#create undefined method `serialize_into_session' for Symbol:Class Here is the

问题 I'm writing a Rails app that uses omniauth-facebook to authenticate the user against FB (and to get a FB OAuth access token for the user). The app then uses Koala to make various calls to the FB Graph API, using that saved OAuth token. I update the saved token each time the user re-authenticates (typically when they log in to my app). Even so, that saved token will expire (or otherwise become invalid) from time to time. What's the best practice around guarding against auth failures and

问题 I have spent days watching the RailsCasts on devise and omniauth and then going through related tutorials for setting up an authentication system that uses these gems. I think the RailsCasts are out of date and trying to patch the gaps with other tutorials is creating all kinds of issues. Please can anyone suggest a current tutorial that I can use as a basis for implementing this system. I have separate user and authentications models (with users having many authentications). I'd really like

问题 So, I just got setup using Rails 3, Devise and OmniAuth via https://github.com/plataformatec/devise/wiki/OmniAuth:-Overview. I'm successfully authenticating users via Facebook, but they are not "rememberable" despite being marked with: devise [...]: rememberable, :omniauthable I tried calling: @the_user.remember_me! ...to no avail. No cookie is being stored/set which means the user does not persist across sessions. Has anybody managed to get a user sourced from FB remembered via cookies? In

问题 I am using rails-4 , and have used OAuth-2 for authentication with Google+ API , for which the following gems are used, in my app: omniauth-oauth2 omniauth-google-oauth2 I have received the following prior email notice: On March 7, 2019, all Google+ APIs and Google+ Sign-in will be shut down completely. This will be a progressive shutdown, with API calls starting to intermittently fail as early as January 28, 2019, and OAuth requests > for Google+ scopes starting to intermittently fail as

问题 I'm developing a Sinatra app for which I'd like to use OmniAuth. So far, I have something similar to this for the web app: http://codebiff.com/omniauth-with-sinatra I'd like the web app to be usable via Android phones which would use an API, authenticating by means of a token. The development of an API seems to be covered nicely here: Sinatra - API - Authentication What is not clear is now I might arrange the login procedure. Presumably it would be along these lines: User selects what service

问题 I'd like to use Omniauth 2 gem to authenticate users, but my problem is the callback uri contains the nginx used port 8082, which is hidden to outside. That's why the auth provider would like to redirect the user to hostname:8082, which is dropped. I tried to rewrite http header, change X-Forwarded-Port, Host, Server-Port attributes (I checked my request object in Rails, and the Server-Port contained the 8082 port number only), but no success. I don't want to modify my application's code, I

问题 I have a custom OAuth2 strategy in my application which I'm using with Omniauth to authorize users from several sites. (These sites are all different installations of the same application, also maintained in-house here, so I have access to both sides of the authorization.) Rather than set up a new strategy for each site, we're using the request phase of the Omniauth cycle to update the strategy with e.g. a new client_secret and client_options at request time. We can distinguish between the