Extends loopback-component-passport to support custom auth schemes (i.e. other than the supported 'ldap', 'local', 'oauth', 'oauth1', 'oauth 1.0', 'openid', 'openid connect' and 'oauth 2.0')

$ npm install --save loopback-component-auth

(the --save option saves it as dependency in your package.json).

This module's main export is a function that follows the component contract defined in loopback. With that said, you can configure this components declaratively in component-config.json or require this module in a boot script and call the exported function with your app object as well as options.

{
  "loopback-component-auth": {
    "serverBaseUrl": "https://secure.my-server.com"
  }
}

'use strict';

const authComponent = require('loopback-component-auth');
const authOptions = { serverBaseUrl: 'https://secure.my-server.com' };

module.exports = function bootAuthComponent(app) {
  authComponent(app, authOptions);
}

When loading this Loopback Component, it will use oniyi-config with { basePath: options.appRootDir + 'authentication', module: 'providers' }. With that said, you can configure all your authentication providers in files located e.g. at 'server/authentication' following the pattern providers.[environment].(json|js). The environment part is optional. Possible values are anything you can set in process.env.NODE_ENV. For file name resolution, process.env.NODE_ENV will be transformed to lower-case.
One special environment is local. It will always be loaded last.

Sample load order (with provess.env.NODE_ENV === 'development'):

1. 'providers.json'
2. 'providers.js'
3. 'providers.development.json'
4. 'providers.development.js'
5. 'providers.local.json'
6. 'providers.local.js'

Note: As files with extension json will always be loaded before files with extension js, you can provide the same file name with different extensions (meaning js will overwrite json files).

Those providers can then be either of the loopback third-party providers or a custom type with your own verify function according to the passport documentation

See server/authentication for an example

{
  "w3-connections": {
    "authScheme": "ibm-connections-basic",
    "module": "passport-ibm-connections-basic",
    "json": true,
    "session": false,
    "authHostname": "w3-connections.ibm.com",
    "openSocial": "/common"
  }
}

sessions (including passport session middleware) are disabled per default.

• disabled (boolean) - default: false; when set to true, provider will not be registered
• link (boolean)
• module
• strategy (string) - default: "Strategy"; name of the module's exported Property to be used as Passport Strategy
• json
• session

• makeLoginCallback (function) - receives single argument of type function (the "done" handler from passport's verify function). Must return function that takes (err, user, identity, token) as arguments and finally calls done(err, user, authInfo) according to the passport documentation. Purpose of the returned function is to serve as callback for UserIdentityModel.login(), which is documented here

• passReqToCallback
• successRedirect (generated for non-json providers only, uses frontendBaseUrl as base url)
• failureRedirect (generated for non-json providers only, uses frontendBaseUrl as base url)
• domain
• scope
• failureFlash
• authInfo

routeName: any. one route with name 'auth' is always created.

• path - - computed to: ${contextRoot}/${providerName}/${routeName}; path to register authenticate or authorize controller
• method - (String) - Allows values of 'GET' and 'POST', defaults to 'GET' when provided value doesn't match one of the allowed values case-insensitively; method to register authenticate or authorize controller
• bodyParser (string) - required when method === 'POST', must be one the parsers provided by body-parser module
• bodyParserOptions (object) - optional; passed to bodyParser['bodyParser'](bodyParserOptions)
• middleware (function)

Apache-2.0 © Benjamin Kroeger