node package manager

passport-facebook-token

Facebook token authentication strategy for Passport

passport-facebook-token

Passport strategy for authenticating with Facebook access tokens using the OAuth 2.0 API.

This module lets you authenticate using Facebook in your Node.js applications. By plugging into Passport, Facebook authentication can be easily and unobtrusively integrated into any application or framework that supports Connect-style middleware, including Express.

$ npm install passport-facebook-token

The Facebook authentication strategy authenticates users using a Facebook account and OAuth 2.0 tokens. The strategy requires a verify callback, which accepts these credentials and calls done providing a user, as well as options specifying a app ID and app secret.

var FacebookTokenStrategy = require('passport-facebook-token');
 
passport.use(new FacebookTokenStrategy({
    clientID: FACEBOOK_APP_ID,
    clientSecret: FACEBOOK_APP_SECRET
  }, function(accessTokenrefreshTokenprofiledone) {
    User.findOrCreate({facebookId: profile.id}, function (erroruser) {
      return done(error, user);
    });
  }
));

Use passport.authenticate(), specifying the 'facebook-token' strategy, to authenticate requests.

app.post('/auth/facebook/token',
  passport.authenticate('facebook-token'),
  function (reqres) {
    // do something with req.user 
    res.send(req.user? 200 : 401);
  }
);

Or using Sails framework:

// api/controllers/AuthController.js 
module.exports = {
  facebookfunction(reqres) {
    passport.authenticate('facebook-token', function(erroruserinfo) {
      // do stuff with user 
      res.ok();
    })(req, res);
  }
};

Clients can send requests to routes that use passport-facebook-token authentication using query parms, body, or HTTP headers. Clients will need to transmit the access_token and optionally the refresh_token that are received from facebook after login.

GET /auth/facebook/token?access_token=<TOKEN_HERE>

Clients can choose to send the access token using the Oauth2 Bearer token (RFC 6750) compliant format

GET /resource HTTP/1.1
Host: server.example.com
Authorization: Bearer base64_access_token_string

optionally a client can send via a custom (default access_token) header

GET /resource HTTP/1.1
Host: server.example.com
access_token: base64_access_token_string

Clients can transmit the access token via the body

GET /resource HTTP/1.1
Host: server.example.com
 
access_token=base64_access_token_string

The MIT License (MIT)

Copyright (c) 2015 Nicholas Penree

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.