GameSaver - a server to save games as JSON blobs using browserId for identification
This repo is a fork of MyFavoriteBeer being used as the basis for a prototype game-saving server written in node.js that uses BrowserID and a simple game that uses this server to save games. See our Pivotal Tracker Project where we've seeded some initial user stories for implementation.
At this moment, almost everything in this repo (including the rest of this file) is exactly the same as the original repo, and relevant to remembering beer but not to saving games. If this project is successful, that will change!
BrowserID is a distributed system that allows users to use their email address as login name and password. The cryptography which allows users to prove that they own an email address without site specific passwords is described in depth in the how browserid works blog post. For website owners, there is a three step tutorial that helps you integrate browserid as fast as possible.
This repository goes into greater depth than the tutorial, and provides a full working example of a small but complete website that uses BrowserID for authentication. This code is running at myfavoritebeer.org.
MyFavoriteBeer is a simple site that allows a user to log in and store a single string
of information, their favorite beer. The site consists of a static HTML frontend
a simple web services API implemented by a node.js server (code under
The web services api exported by the node.js server consists of the following:
/api/whoami- reports whether the current session is authenticated
/api/login- accepts a browserid assertion to allow the user to authenticate
/api/get- returns the current user's favorite beer
/api/set- sets the current user's favorite beer
/api/logout- clears the current session
Further documentation of these calls is available in the source code.
The most interesting part of this example is how authentication occurs. Client code
navigator.id.getVerifiedEmail() is invoked. BrowserID returns a string
which contains an assertion. This assertion is passed up to the myfavoritebeer server
/api/login api. The server verifies this assertion using the free
verifier service by
https://browserid.org/verify. Finally, upon successful
verification, the server sets a cookie which represents an authenticated session.
For simplicities' sake, "sessions" in this example are implemented using a third party library which encrypts session data using a private key and stores this data in a cookie on the user's browser. This approach makes it so the server doesn't need to store any data to implement sessions and keeps the example simple.
We have to store the beer preferences somewhere. mongodb is used for this purpose and
a very simple database abstraction layer exists in
db.js. The details of interacting
with the database aren't important, but if you're curious have a look in db.js.
To run the example code locally:
- clone this repository
- install node (0.4.7+) and npm.
On stdout you'll see an ip address and port, like
127.0.0.1:59275. Open that
up in your web browser.
NOTE: You'll see warnings about how no database is configured. Don't worry about it. The code is designed to run with or without a configured database so that it's easier to play with. The only downside of running without a database is that your server won't remember anything. Oh well.
The code is designed to run on heroku's node.js hosting services, and the only way
this affects the implementation is via environment variable naming choices and
the presence of a
Procfile which tells heroku how to start the server.
If you'd like to deploy this service to heroku yourself, all you'd have to do is:
- set up a heroku account (and run through their tutorial)
- add a free mongolab instance (for persistence):
heroku addons:add mongolab:starter
- set your app to bind to all available ips:
heroku config:add IP_ADDRESS=0.0.0.0
- set a random string to encrypt cookies:
heroku config:add SEKRET=<long random string>
- push the code up to heroku!
NOTE: While the sample is targeted at heroku, with minimal code modifications it should run under the hosting environment of your preference.