sp-auth-config - Config options builder for sp-auth (SharePoint Authentication in Node.js)

sp-auth-config provides wizard-like approach for building and managing config files for sp-auth (Node.js to SharePoint unattended http authentication). Includes CLI for generating config files from command prompt. This is fork from the original repository node-sp-auth. Where un-needed functionality has been removed, and some customization hs been made to better work with FMV sharepoint.

Versions supported:

• SharePoint 2019
• SharePoint 2016
• SharePoint 2013

Authentication options:

• SharePoint 2019, 2016, 2013:
  • Form-based authentication (Forefront TMG)
    • Sharepoint-url
    • Username
    • Password
    • Curl

How to use

Usage in TypeScript

import { AuthConfig } from 'node-sp-auth-config';

const authConfig = new AuthConfig({
  configPath: './config/private.json',
  encryptPassword: true,
  saveConfigOnDisk: true
});

authConfig.getContext()
  .then((context) => {
    console.log(JSON.stringify(context, null, 2));
    // context.authOptions - node-sp-auth authentication options
  })
  .catch(console.warn);

Usage in JavaScript

const AuthConfig = require('node-sp-auth-config').AuthConfig;

const authConfig = new AuthConfig({
  configPath: './config/private.json',
  encryptPassword: true,
  saveConfigOnDisk: true
});

authConfig.getContext()
  .then((context) => {
    console.log(JSON.stringify(context, null, 2));
    // context.authOptions - node-sp-auth authentication options
  })
  .catch(console.warn);

Initiation parameters

Parameter	Default value	Description
configPath	'./config/private.json'	Path to auth config .json
encryptPassword	true	Encrypt password to a machine-bind hash
saveConfigOnDisk	true	Save config .json to disk
forcePrompts	false	Force parameters prompts
headlessMode	false	Prevents interactive prompts - for headless, CI/CD processes
defaultConfigPath	empty	Path to .json config, parameters from which are placed as defaults
authOptions	empty	Any valid node-sp-auth options

Production runtime

Headless mode

When using in a headless mode, in case of missing parameters, one can expect non-interactive behavior with no prompts but graceful exit with corresponding error output.

This can be achieved by providing headlessMode settings property is equal to true.

The headless mode also automatically configured when NODE_ENV (or SPAUTH_ENV) environment variable is equal to production.

Environment variables

All the parameters which are usually stored in private.json can be defined also using environment variables. Environment variables started with SPAUTH_ prefix are recognized with the library. Second part of the name is an actual name of the node-sp-auth credentials property yet in uppercase (e.g. SPAUTH_SITEURL, SPAUTH_USERNAME, SPAUTH_PASSWORD).

Along with credentials props these service variables are used:

Variable	Description
NODE_ENV	When equal to production forces headlessMode.
SPAUTH_ENV	When equal to production forces headlessMode. Overwrites NODE_ENV.
SPAUTH_FORCE	Makes SPAUTH_{CREDENTIALS} variables take precedence over those possibly stored in private.json.

License

MIT License

Copyright (c) 2017-2018 Andrew Koltyakov