Actions
Workbench authentication process » History » Revision 12
« Previous |
Revision 12/26
(diff)
| Next »
Peter Amstutz, 11/17/2014 06:55 PM
Workbench authentication process¶
- In workbench, when the user goes to a page, it checks for a session or
?api_token=xxx
in the URL for the API token. If no API token is found, the user is directed to the workbench "welcome" page. - In workbench, the "welcome" page has a "log in" button that directs the user to the API server login URL, with a
?return_to=xxx
link embedded in the URL. - In API server, the 'login' endpoint goes to
UserSessionsController#login
in the API server. This redirects to/auth/joshid?return_to=xxx
- In API server,
/auth/joshid
is intercepted by the OmniAuth Rack middleware and invokes thejosh_id
OmniAuth strategy.- The
josh_id
OmniAuth strategy is implemented inarvados/services/api/lib/josh_id.rb
and is a subclass ofOmniAuth::Strategies::OAuth2
- OmniAuth starts the "request_phase" of
OmniAuth::Strategies::OAuth2
. This redirects to#{options[:custom_provider_url]}/auth/josh_id/authorize
using CUSTOM_PROVIDER_URL defined inarvados/services/api/config/initializers/omniauth.rb
- The
- In sso-provider,
/auth/josh_id
is routed toAuthController#authorize
, and is intercepted bybefore_filter :authenticate_user!
(part of the devise gem)- devise is configured at
sso-provider/config/initializers/devise.rb
devise :omniauthable, :omniauth_providers => [:google]
configuressso-provider/app/models/user.rb
authenticate_user!
is not explicitly defined but instead monkey patched into the controller indevise/lib/devise/controllers/helper.rb
authenticate_user!
callswarden.authenticate!
(warden/lib/warden/proxy.rb
) with a scope of:user
(warden is another Rack-based authentication gem)- Warden proxy tries the TokenAuthenticatable and DatabaseAuthenticatable strategies, but these strategies fail and it raises a :warden exception. This causes it to call
failure_app
which is set up indevise/lib/devise.rb
to beDevise::Delegator.new
- This maps to
devise/lib/devise/failure_app.rb
which redirects to the new_user_session_path/users/sign_in
which routes to the SSOSessionsController#new
which subclassesDevise::SessionsController
- devise is configured at
- In sso-provider,
SessionsController#new
redirects to/users/auth/google
Questions¶
- What is workbench's "secret_token" for?
Updated by Peter Amstutz about 10 years ago · 26 revisions