Wires up the common auth handlers for Artsy's [Ezel]( apps using [passport](

npm install artsy-passport
22 downloads in the last week
37 downloads in the last month

Artsy Passport

Wires up the common auth handlers for Artsy's ezel-based apps using passport. Used internally at Artsy to DRY up authentication code.


Make sure you first mount session, body parser, and xapp middlware.

app.use require('artsy-xapp-middlware') { #... }
app.use express.bodyParser()
app.use express.cookieParser('foobar')
app.use express.cookieSession()

Then mount Artsy Passport passing a big configuration hash.

Values indicate defaults.

app.use artsyPassport
  FACEBOOK_ID: # Facebook app ID
  FACEBOOK_SECRET: # Facebook app secret
  TWITTER_KEY: # Twitter consumer key
  TWITTER_SECRET: # Twitter consumer secret
  ARTSY_ID: # Artsy client id
  ARTSY_SECRET: # Artsy client secret
  SECURE_ARTSY_URL: # SSL Artsy url e.g.
  APP_URL: # Url pointing back to your app e.g.
  facebookPath: '/users/auth/facebook' # Url to point your facebook button to
  twitterPath: '/users/auth/twitter' # Url to point your twitter button to
  loginPath: '/users/sign_in' # POST `email` and `password` to this path to login
  signupPath: '/users/invitation/accept' # POST `email` and `password` to this path to signup
  twitterCallbackPath: '/users/auth/twitter/callback' # After twitter auth callback url
  facebookCallbackPath: '/users/auth/facebook/callback' # After facebook auth callback url
  # The user data to cache in the session
  userKeys: ['id', 'type', 'name', 'email', 'phone', 'lab_features', 'default_profile_id']
  CurrentUser: # Backbone Model class to serialize the user into e.g. `CurrentUser`
  # Temporary generated email for twitter signup.
  twitterSignupTempEmail: (token, secret, profile) -> ''
  # (optional) After signing up with a provider Artsy Passport will redirect to the
  # login url. Override this to intecerpt with your own path such as a UI to prompt
  # for an email address to replace the Twitter temporary email. Just make sure that
  # UI will then redirect to `twitterPath` to log in via twitter.
  twitterSignupPath: this.twitterPath
  facebookSignupPath: this.facebookPath

The keys are cased so it's convenient to pass in a configuration hash. A minimal setup could look like this:

app.use artsyPassport _.extend config,
  CurrentUser: CurrentUser

Create login and signup forms pointing to your paths.

h1 Login
a( href='/users/auth/facebook' ) Login via Facebook
a( href='/users/auth/twitter' ) Login via Twitter
form( action='/users/sign_in', method='POST' )
  h3 Login via Email
  input( name='name' )
  input( name='email' )
  input( name='password' )
  button( type='submit' ) Signup

h1 Signup
a( href='/users/auth/facebook?sign_up=true' ) Signup via Facebook
a( href='/users/auth/twitter?sign_up=true' ) Signup via Twitter
form( action='/users/invitation/accept', method='POST' )
  h3 Signup via Email
  input( name='name' )
  input( name='email' )
  input( name='password' )
  button( type='submit' ) Signup

Handle login and signup callbacks.

{ loginPath, signupPath, twitterCallbackPath,
  facebookCallbackPath } = artsyPassport.options loginPath, (req, res) ->
  res.redirect '/' signupPath, (req, res) ->
  res.redirect '/personalize'
app.get twitterCallbackPath, (req, res) ->
  if req.query.sign_up then res.redirect('/personalize') else res.redirect('/')
app.get facebookCallbackPath, (req, res) ->
  if req.query.sign_up then res.redirect('/personalize') else res.redirect('/')

Access a logged in Artsy user in a variety of ways...

In your server-side templates

h1 Hello #{user.get('name')}

In your client-side code

CurrentUser = require '../models/'
sd = require('sharify').data

user = new CurrentUser(sd.CURRENT_USER)

In your routers

app.get '/', (req, res) ->
  res.send 'Hello ' + req.user.get('name')

These forms of user will be null if they're not logged in.


First install node modules npm install then write a ./ that looks something like this:

module.exports =
  ARTSY_ID: ''
  APP_URL: ''
  # An Artsy user that's linked to facebook and twitter

Then you can check the example by running make example and opening localhost:4000. The tests are integration tests that use the example, so once you set this up run make test to run tests.

npm loves you