New Research: Supply Chain Attack on Axios Pulls Malicious Dependency from npm.Details →
Socket
Book a DemoSign in
Socket

hapi-auth-basic-key

Package Overview
Dependencies
Maintainers
1
Versions
5
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

hapi-auth-basic-key

Basic api-key-as-username authentication plugin

latest
Source
npmnpm
Version
6.0.0
Version published
Maintainers
1
Created
Source

hapi-auth-basic-key

Node.js CI

Fork of hapi-auth-basic that is intended to handle API keys as the username field of HTTP basic auth requests. The password portion of the authorization is available, but not required. Could be useful for session tokens.

Changes in v6.0.0-key

  • Rebased on @hapi/basic v6.0.0
  • Supports Node 12+
  • Supports Hapi v18+

Basic authentication requires validating a username and password combination. The 'basic' scheme takes the following options:

  • validate - (required) a user lookup and password validation function with the signature [async] function(request, username, password, h) where:
    • request - is the hapi request object of the request which is being authenticated.
    • username - the username (api key) received from the client.
    • password - (optional) the password received from the client. Useful for session tokens.
    • h - the response toolkit.
    • Returns an object { isValid, credentials, response } where:
      • isValid - true if both the username was found and the password matched, otherwise false.
      • credentials - a credentials object passed back to the application in request.auth.credentials.
      • response - Optional. If provided will be used immediately as a takeover response. Can be used to redirect the client, for example. Don't need to provide isValid or credentials if response is provided
    • Throwing an error from this function will replace default Boom.unauthorized error
    • Typically, credentials are only included when isValid is true, but there are cases when the application needs to know who tried to authenticate even when it fails (e.g. with authentication mode 'try').
  • allowEmptyUsername - (optional) if true, allows making requests with an empty username. Defaults to false.
  • unauthorizedAttributes - (optional) if set, passed directly to Boom.unauthorized if no custom err is thrown. Useful for setting realm attribute in WWW-Authenticate header. Defaults to undefined.
const Hapi = require('hapi');

const keys = {
    SUPER_SECRET_API_KEY: { // <-- Your API key
        name: 'Your Api Key Name',
        id: '2133d32a'
    }
};

const validate = async (request, username, password, h) => {
    
    const key = keys[username]; // username=api key
    if (!key) {
        return { credentials: null, isValid: false };
    } 
    
    // could further validate password if using it as a session token or something
    
    return { credentials: key, isValid: true };
};

const main = async () => {

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

    await server.register(require('hapi-auth-basic-key'));

    server.auth.strategy('simple', 'basic', { validate });
    server.auth.default('simple');

    server.route({
        method: 'GET',
        path: '/',
        handler: function (request, h) {

            return 'welcome';
        },
        // config: { auth: 'simple' } // if not applied globally
    });

    await server.start();

    return server;
};

main().then((server) => console.log(`Server listening on ${server.info.uri}`)).catch((err) => {

    console.error(err);
    process.exit(1);
});

Keywords

hapi

FAQs

Package last updated on 22 Mar 2022

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts