The kerberos package is a C++ extension for Node.js that provides cross-platform support for kerberos authentication using GSSAPI on linux/osx, and SSPI on windows. Much of the code in this module is adapted from ccs-kerberos and winkerberos.

Linux

• python v2.7
• make
• A proper C/C++ compiler toolchain, like GCC
• Distribution-specific kerberos packages (e.g. krb5-dev on Ubuntu)

macOS

• Xcode Command Line Tools: Can be installed with xcode-select --install
• Distribution-specific kerberos packages (e.g. krb5 on Homebrew)

Windows

• Option 1: Install all the required tools and configurations using Microsoft's windows-build-tools by running npm install -g windows-build-tools from an elevated PowerShell (run as Administrator).

• Option 2: Install dependencies and configuration manually

  1. Visual C++ Build Environment:
  • Option 1: Install Visual C++ Build Tools using the Default Install option.
  • Option 2: Install Visual Studio 2015 (or modify an existing installation) and select Common Tools for Visual C++ during setup.

  💡 [Windows Vista / 7 only] requires .NET Framework 4.5.1

  2. Install Python 2.7 or Miniconda 2.7 (v3.x.x is not supported), and run npm config set python python2.7
  3. Launch cmd, npm config set msvs_version 2015

Now you can install kerberos with the following:

npm install kerberos

Run the test suite using:

npm test

NOTE: The test suite requires an active kerberos deployment, see test/scripts/travis.sh to better understand these requirements.

Release a new version of the extension by:

1. Run npm run release
2. Run git push --follow-tags origin main
3. The release will be created in Github automatically by the CD pipeline, go to it and download the package artifact (tgz)
4. Run npm publish <path to tarball>

KerberosClient

KerberosServer

checkPassword(username, password, service, [defaultRealm], [callback]) ⇒ Promise

This function provides a simple way to verify that a user name and password match those normally used for Kerberos authentication. It does this by checking that the supplied user name and password can be used to get a ticket for the supplied service. If the user name does not contain a realm, then the default realm supplied is used.

For this to work properly the Kerberos must be configured properly on this machine. That will likely mean ensuring that the edu.mit.Kerberos preference file has the correct realms and KDCs listed.

IMPORTANT: This method is vulnerable to KDC spoofing attacks and it should only be used for testing. Do not use this in any production system - your security could be compromised if you do.

principalDetails(service, hostname, [callback]) ⇒ Promise

This function returns the service principal for the server given a service type and hostname.

Details are looked up via the /etc/keytab file.

initializeClient(service, [options], [callback]) ⇒ Promise

Initializes a context for client-side authentication with the given service principal.

initializeServer(service, [callback]) ⇒ Promise

Initializes a context for server-side authentication with the given service principal.

Properties

• KerberosClient

  • .step(challenge, [callback])

  • .wrap(challenge, [options], [callback])

  • .unwrap(challenge, [callback])

Processes a single kerberos client-side step using the supplied server challenge.

Returns: Promise - returns Promise if no callback passed

Perform the client side kerberos wrap step.

Returns: Promise - returns Promise if no callback passed

Perform the client side kerberos unwrap step

Returns: Promise - returns Promise if no callback passed

Properties

Processes a single kerberos server-side step using the supplied client data.

Returns: Promise - returns Promise if no callback passed

This function provides a simple way to verify that a user name and password match those normally used for Kerberos authentication. It does this by checking that the supplied user name and password can be used to get a ticket for the supplied service. If the user name does not contain a realm, then the default realm supplied is used.

For this to work properly the Kerberos must be configured properly on this machine. That will likely mean ensuring that the edu.mit.Kerberos preference file has the correct realms and KDCs listed.

IMPORTANT: This method is vulnerable to KDC spoofing attacks and it should only be used for testing. Do not use this in any production system - your security could be compromised if you do.

Returns: Promise - returns Promise if no callback passed

This function returns the service principal for the server given a service type and hostname.

Details are looked up via the /etc/keytab file.

Returns: Promise - returns Promise if no callback passed

Initializes a context for client-side authentication with the given service principal.

Returns: Promise - returns Promise if no callback passed

Initializes a context for server-side authentication with the given service principal.

Returns: Promise - returns Promise if no callback passed