devise_oauth_token_authenticatable

devise_oauth_token_authenticatable

There are plenty of gems out there that deal with being an OAuth2 "consumer", where you redirect users to an OAuth2 "provider", allowing you to hand off authentication to a separate service. There are also plenty of gems that set you up as your own OAuth2 provider. ***BUT***, what happens when you want to separate your "authentication" server from your "resource" server? This gem is meant to be used on an API "resource" server, where you want to accept OAuth Access Tokens from a client, and validate them against a separate "authentication" server. This communication is outside the scope of the official OAuth 2 spec, but there is a need for it anyway.

Rubygem devise_oauth_token_authenticatable

Total Downloads
1881
Releases
2
Current Version
0.0.2
Released
2012-08-06 00:00:00 UTC
First Release
2012-07-09 07:00:00 UTC
Depending Gems
0

Github mleglise/devise_oauth_token_authenticatable

Watchers
4
Forks
0
Development activity
Inactive
Last commit
2012-08-06 23:50:58 UTC
First commit

Resources

There are no resources yet, be the first to submit one!

Comments

There are no comments yet, be the first to write one!

Post a comment

Markdown supported
or
×

In order to continue, you must be signed in using your Github account.

If you're signing in using this account for the first time Github will ask for your permission to give access to your public user data to the Ruby Toolbox.

Although the Github Authorization page does not mention it, the request includes read-only access to your verified email address (user:email OAuth scope). This is neccessary so there's a way to notify you about comments, information about your accepted project edits and the like. You can review your notification settings on your account page once you're signed in.