Skip to content


Subversion checkout URL

You can clone with
Download ZIP
A paired consumer (client) / provider (server) example of OAuth2 for NodeJS
branch: master

NodeJS OAuth2 Example

git clone git://
pushd node-oauth2-examples
npm install -g grunt-cli
npm install

There are two servers: provider and consumer.

For running this demo on localhost you should edit /etc/hosts and use something like and as aliases of Currently there's a bug that I don't understand that prevents the demo from working on localhost.

Bookface (Provider)

pushd bookface-provider/
npm install
grunt build
node bookface-provider/bin/provider

Blogthing (Consumer)

pushd blogthing-consumer/
npm install
grunt build
node blogthing-consumer/bin/consumer

Demo (runs both)

node bin/demo

Provider (Bookface)

A provider is a service like facebook, twitter, google+, or github that handles the details of authentication.


  • http://localhost:4455/login
  • http://localhost:4455/logout
  • http://localhost:4455/secret

Consumer (Blogthing)

The consumer is a service such as Disqus, Spotify, EverNote, BlissControl, IfThisThenThat, or Calepin


  • http://localhost:7788/login
  • http://localhost:4455/logout
  • http://localhost:4455/secret


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 allow / deny prompt.


The provider is an application platform such as Facebook, Google, and Twitter.

The consumer is an application registered with the platform such as StackOverflow or TweetDeck.

RESTful resources

  • The authorize is usually something like oauth/authorize such as
  • The access_token is usually something like oauth/access_token such as


scope is arbitrary data. For example you might allow other apps to access things like

  • email address
  • contacts
  • birthday
  • friends

In which case you might publish your API in such a way that when you have a request where you 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.

client_id (and secret)

You should have some registration process by which you give the application an id and a secret.

The 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 provider POSTs the code to the consumer. 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.


Dipping into auth_middleware Dipping into requestMethods Dipping into strategyExecutor Dipping into foostrategy

Something went wrong with that request. Please try again.