This is an exploratory demo with both an OAuth2 provider and consumer. The demo provider lets you login and can grant access to the consumer.
You should clone it to play.
git clone git://github.com/coolaj86/node-oauth2-examples.git cd node-oauth2-examples npm install
node bin/provider # runs server/lib/provider.js # uses oauth2-provider # http://localhost:4455/login # http://localhost:4455/logout # http://localhost:4455/secret
node bin/consumer # runs server/lib/consumer.js and foo-oauth2-strategy.js # uses connect-auth and node-oauth # http://localhost:7788/login
The demo consumer will ask the provider to log you in.
If you have already logged in to the provider you don't need to login again,
instead you will be directly taken to the
P.S. It's almost 3am. I'll finish these docs sometime later. The code is pretty clean, but still has some ugly in it (mostly from the examples I copied and haven't refactored well-enough yet)
The provider is an application platform such as Facebook, Google, and Twitter.
The consumer is an application registered with the platform such as TweetDeck.
- The authorize is usually something like
- The access_token is usually something like
scope is arbitrary data. For example you might allow other apps to access things like
- email address
In which case you might publish your API in such a way that when you have a request where
encodeURI the string
["email","contacts","birthday"] and then present a user interface
telling the user that the application wants access to their email address, contacts, and birthday.
If the app needs access to more permissions in the future it might make another request with a larger scope.
You should have some registration process by which you give the application an
id and a
client_id will be sent in the clear and is the id you need to look up in your database.
The secret is handled by the
oauth library for cookies or something like that.
This will be
web_server for all web servers.
If you were writing an android app it would probably be something different.
This is the uri to which the
code to the
This logic should be handled by the
strategy, but leave the storage abstraction up to you.
There is an additional callback provided by the
strategy which your app should respond to.
Don't get the two mixed up. :-D
This is the query parameter used as the provider responds to the request for an access token.