kotovalexarian-likes-github
/
omniauth--omniauth
mirror of https://github.com/omniauth/omniauth.git
1
0
Fork 0
Code Releases Activity
OmniAuth is a flexible authentication system utilizing Rack middleware.
904 Commits 11 Branches 66 Tags 4 MiB
Ruby 98.5%
CSS 1.5%
Go to file
Michael Bleigh 69177f3b10 Moves omniauth/core to just plain omniauth 2011-09-22 13:25:41 -05:00
lib Moves omniauth/core to just plain omniauth 2011-09-22 13:25:41 -05:00
spec Moves omniauth/core to just plain omniauth 2011-09-22 13:25:41 -05:00
.gemtest Gem dependency refactor 2011-04-22 02:52:52 -05:00
.gitignore Ignore lots of stuff that should be ignored 2011-05-09 21:33:18 -07:00
.rspec Switch to progress format to make Travis builds easier to read etc. 2011-04-25 10:22:29 -05:00
.travis.yml Revert "Remove JRuby support" 2011-08-08 13:45:50 -07:00
.yardopts Gem dependency refactor 2011-04-22 02:52:52 -05:00
Gemfile Rename and prepare gemspec, add guard to Gemfile (but not gemspec). 2011-09-03 21:31:52 -03:00
Guardfile Rename and prepare gemspec, add guard to Gemfile (but not gemspec). 2011-09-03 21:31:52 -03:00
LICENSE Merging master. 2011-09-03 15:08:07 -03:00
README.md Update README with 1.0 info 2011-09-03 21:48:27 -03:00
Rakefile Clearing out everything to move towards the new 1.0 independent gems strategy. 2011-09-03 21:26:57 -03:00
omniauth.gemspec Rename and prepare gemspec, add guard to Gemfile (but not gemspec). 2011-09-03 21:31:52 -03:00

README.md

OmniAuth: Standardized Multi-Provider Authentication

NOTICE: This documentation and code is toward OmniAuth 1.0 in which each provider will become its own separate gem. If you're looking for the current released version, please visit OmniAuth 0.3 Stable Branch.

Structural Changes Coming in 1.0

In version 1.0, the omniauth gem will become simply the underlying framework upon which authentication strategies can be built. That means where once users would put gem 'omniauth' into their Gemfile and be finished, now each provider will have a separate gem (e.g. oa-twitter).

This change will bring about better code, faster releases, and hopefully an even more vibrant provider landscape. For more on the rationale of the change, see this issue.

Technical Changes Coming in 1.0

The AuthHash Class

In the past, OmniAuth has provided a simple hash of authentication information. In 1.0, the returned data will be an AuthHash, a special kind of hash that has extra properties special to OmniAuth. In addition, the auth hash schema will be changing slightly. More on that soon.

Universal Options

In 1.0, it will be possible to set certain configuration options that will then apply to all providers. This will make certain things easier.

Simpler Dynamic Workflow

To date, the workflow for "dynamic" providers (being able to change them at runtime) has been somewhat difficult. We will be re-evaluating this process and making sure it's as good as it can be.

Declarative Provider Authorship

We hope to provide a more declarative provider authorship system that will make it both easier to write and easier to test strategies. Much of this may have to be implemented in "aggregate" strategy providers such as OAuth and OAuth2, but stay tuned for more on this.

Testing, Testing, Testing!

OmniAuth 1.0 will be strongly tested and solid. Because we can release it one piece at a time (starting with the core gem and expanding out into the other provider gems) we will be able to maintain much higher code quality and the project will generally be more manageable.

Stay Tuned!

OmniAuth 1.0 is a work in progress. We will keep the community updated about progress as we have more information. Thanks!

License

OmniAuth is released under the MIT License.