Unleash the Power of OmniAuth Callbacks Passthrough for Seamless Authentication

I recently spent about 4 hours struggling to figure out how to adapt my Devise/Omniauth request before the authorize redirect. I'm having trouble connecting my Devise Token Auth with a token I get back from google in react. I'm using this package for the button: https:// ... ... omniauth_callbacks#passthru user_facebook_omniauth_callback GET|POST /users/auth/facebook/callback(.:format) devise/omniauth_callbacks#facebook. ... passthru user_facebook_omniauth_callback GET|POST /users/auth/facebook/callback(.:format) devise/omniauth_callbacks#facebook ... draw do - devise_for :users + ... :format) devise/omniauth_callbacks#passthru {:provider=>/facebook/} user_omniauth_callback GET|POST /users/auth/:action/callback(.:format) ... Authentication passthru after ... I found that is caused by the controller for :omniauth_callbacks in devise route is not specified. I'm using Devise with Omniauth. It doesn't seem possible to restrict the initial user auth requests to only GET's or only POST's. Is it? # Gemfile gem 'devise' gem 'devise-i18n' gem 'omniauth', '~> 2.1 ... { omniauth_callbacks: 'users/omniauth_callbacks' } end. 视图(涡轮部分 ... However - when setting up the actual Devise integration - it does use the name parameter in the specified args . ... omniauth_callbacks#passthru ... Method: Devise::OmniauthCallbacksController#passthru. Defined in: app/controllers/devise/omniauth_callbacks_controller.rb ...