Skip to content

HTTP Bearer authentication strategy, with optional base64 encoded token support, for Passport and Node.js.

License

Notifications You must be signed in to change notification settings

auralon/passport-http-bearer-base64

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

61 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

passport-http-bearer-base64

Build Coverage Dependencies

HTTP Bearer authentication strategy for Passport.

This module lets you authenticate HTTP requests using bearer tokens, as specified by RFC 6750, in your Node.js applications. However, we also provide support for base64 encoded tokens (which is not in the spec). Bearer tokens are typically used protect API endpoints, and are often issued using OAuth 2.0.

By plugging into Passport, bearer token support can be easily and unobtrusively integrated into any application or framework that supports Connect-style middleware, including Express.

Install

$ npm install passport-http-bearer-base64

Usage

Configure Strategy

The HTTP Bearer authentication strategy authenticates users using a bearer token. The strategy requires a verify callback, which accepts that token credential and calls done providing a user. Optional info can be passed to the callback, typically including associated scope, which will be set by Passport at req.authInfo to be used by later middleware for authorization and access control.

passport.use(new BearerStrategy(
  function(token, done) {
    User.findOne({ token: token }, function (err, user) {
      if (err) { return done(err); }
      if (!user) { return done(null, false); }
      return done(null, user, { scope: 'all' });
    });
  }
));

There are a couple of options that can be set when instantiating the bearer strategy...

  • passReqToCallback (boolean) - default false
    • If set to true then req will be passed as the first argument to the verify callback.
  • base64EncodedToken (boolean) - default false
    • If set to true then incoming bearer tokens are expected to be base64 encoded.

Using these options would change the configuration like so:

passport.use(new BearerStrategy({
    passReqToCallback  : true,
    base64EncodedToken : true
  },
  function(req, token, done) {
    User.findOne({ token: token }, function (err, user) {
      if (err) { return done(err); }
      if (!user) { return done(null, false); }
      return done(null, user, { scope: 'all' });
    });
  }
));

Authenticate Requests

Use passport.authenticate(), specifying the 'bearer' strategy, to authenticate requests. Requests containing bearer tokens do not require session support, so the session option can be set to false.

For example, as route middleware in an Express application:

app.get('/profile', 
  passport.authenticate('bearer', { session: false }),
  function(req, res) {
    res.json(req.user);
  });

Issuing Tokens

Bearer tokens are typically issued using OAuth 2.0. OAuth2orize is a toolkit for implementing OAuth 2.0 servers and issuing bearer tokens. Once issued, this module can be used to authenticate tokens as described above.

Examples

For a complete, working example, refer to the Bearer example [Note: This example is for the bearer token module that this project is forked from. This module is identical apart from the inclusion of base64 encoded token support, so the example is still relevant].

Related Modules

  • OAuth2orize — OAuth 2.0 authorization server toolkit

Tests

$ npm install
$ npm test

Credits

License

The MIT License

Copyright (c) 2011-2013 Jared Hanson <http://jaredhanson.net/> Copyright (c) 2016 Keith Hill <https://bluemantis.com/>

About

HTTP Bearer authentication strategy, with optional base64 encoded token support, for Passport and Node.js.

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • JavaScript 86.1%
  • Makefile 13.9%