Third-party login plugin for hapi
slaawwa and AdriVanHoudt V9.3.2 add config 'fields' to vk provider (#372)
* Add custom fields + fix bug with uid => id

* Update tests + add new test for 'fields'

* Add dynamic key_id

* Add space for travis

* Change vk version for travis

* Change field in Mock data for version low than 5 (for travis)

* Back old test (for travis)
Latest commit 58f0d4a Oct 10, 2018

README.md

bell

Third-party authentication plugin for hapi.

Lead Maintainer: Adri Van Houdt

Build Status

bell ships with built-in support for authentication using Facebook, GitHub, Google, Google Plus, Instagram, LinkedIn, Slack, Stripe, Twitter, Yahoo, Foursquare, VK, ArcGIS Online, Windows Live, Nest, Phabricator, BitBucket, Dropbox, Reddit, Tumblr, Twitch, Mixer, Salesforce, Pinterest, Discord, DigitalOcean, AzureAD, trakt.tv and Okta.

It also supports any compliant OAuth 1.0a and OAuth 2.0 based login services with a simple configuration object.

Sponsor

If you want to add secure authentication to apps or APIs, feel free to check out Auth0's SDKs and free plan at auth0.com/overview.


Documentation

API Documentation

Providers Documentation

Tutorials

Social Login with Twitter using hapi.js

Examples

All Examples

Twitter:

// Load modules

const Bell = require('bell');
const Hapi = require('hapi');


// Declare internals

const internals = {};


internals.start = async function () {

    const server = Hapi.server({ port: 8000 });

    // Register bell with the server

    await server.register(Bell);

    // Declare an authentication strategy using the bell scheme
    // with the name of the provider, cookie encryption password,
    // and the OAuth client credentials.

    server.auth.strategy('twitter', 'bell', {
        provider: 'twitter',
        password: 'cookie_encryption_password_secure',
        clientId: 'my_twitter_client_id',
        clientSecret: 'my_twitter_client_secret',
        isSecure: false     // Terrible idea but required if not using HTTPS especially if developing locally
    });

    // Use the 'twitter' authentication strategy to protect the
    // endpoint handling the incoming authentication credentials.
    // This endpoint usually looks up the third party account in
    // the database and sets some application state (cookie) with
    // the local application account information.

    server.route({
        method: ['GET', 'POST'],    // Must handle both GET and POST
        path: '/login',             // The callback endpoint registered with the provider
        options: {
            auth: 'twitter',
            handler: function (request, h) {

                if (!request.auth.isAuthenticated) {
                    return `Authentication failed due to: ${request.auth.error.message}`;
                }

                // Perform any account lookup or registration, setup local session,
                // and redirect to the application. The third-party credentials are
                // stored in request.auth.credentials. Any query parameters from
                // the initial request are passed back via request.auth.credentials.query.

                return h.redirect('/home');
            }
        }
    });

    await server.start();
};

internals.start();