CSC/ECE 517 Spring 2015/ch1b 21 QW: Difference between revisions
| Line 14: | Line 14: | ||
== Getting Start == | == Getting Start == | ||
Each OmniAuth strategy is a Rack Middleware, which means it can be used the same way as other Rack middleware. To use the built-in Developer strategy in a Sinatra application, the first step is: | Each OmniAuth strategy is a Rack Middleware, which means it can be used the same way as other Rack middleware. To use the built-in Developer strategy in a Sinatra application, the first step is: | ||
=== Add gem to Gemfile === | === Add gem to Gemfile === | ||
<pre> | <pre> | ||
gem 'omniauth-twitter' | gem 'omniauth-twitter' | ||
</pre> | </pre> | ||
== Other Examples == | == Other Examples == | ||
== References == | == References == | ||
<references/> | <references/> | ||
Revision as of 16:55, 16 February 2015
Omniauth
Omniauth is a Ruby authentication framework aimed to integrated with various types of authentication providers. It can be hooked up to any system, from social network to enterprise systems to simple username and password authentication. <ref>https://github.com/intridea/omniauth/wiki</ref>
The topic writeup for this page can be found here.
Background
With web application booming, most users login hundreds of services every day and won't expect to create unique login and password for each service. So intridea recently releases a standard library to provide multi-provider authentication for web applications.
Rack Middleware
Sinatra
Getting Start
Each OmniAuth strategy is a Rack Middleware, which means it can be used the same way as other Rack middleware. To use the built-in Developer strategy in a Sinatra application, the first step is:
Add gem to Gemfile
gem 'omniauth-twitter'
Other Examples
References
<references/>