safeguard.js

One Identity Safeguard JavaScript SDK

Support

One Identity open source projects are supported through One Identity GitHub issues and the One Identity Community. This includes all scripts, plugins, SDKs, modules, code snippets or other solutions. For assistance with any One Identity GitHub project, please raise a new Issue on the One Identity GitHub project page. You may also visit the One Identity Community to ask questions. Requests for assistance made through official One Identity Support will be referred back to GitHub and the One Identity Community forums where those requests can benefit all users.

If you would like to add to safeguard.js? See the developer guide.

Introduction

All functionality in Safeguard is available via the Safeguard API. There is nothing that can be done in the Safeguard UI that cannot also be performed using the Safeguard API programmatically.

safeguard.js is provided to facilitate calling the Safeguard API from JavaScript. It is meant to remove the complexity of dealing with authentication via Safeguard's embedded secure token service (STS). The basic usage is to call connect() to establish a connection to Safeguard, then you can call invoke() multiple times using the same authenticated connection.

safeguard.js also provides an easy way to call Safeguard A2A from JavaScript. The A2A service requires client certificate authentication for retrieving passwords for application integration. When Safeguard A2A is properly configured, specified passwords can be retrieved with a single method call without requiring access request workflow approvals. Safeguard A2A is protected by API keys and IP restrictions in addition to client certificate authentication.

safeguard.js includes an SDK for listening to Safeguard's powerful, real-time event notification system. Safeguard provides role-based event notifications via SignalR to subscribed clients. If a Safeguard user is an Asset Administrator events related to the creation, modification, or deletion of Assets and Asset Accounts will be sent to that user. When used with a certificate user, this provides an opportunity for reacting programmatically to any data modification in Safeguard. Events are also supported for access request workflow and for A2A password changes.

Installation

This javascript module is published to the npm registry to make it as easy as possible to install.

> npm install @oneidentity/safeguard

Getting Started

A simple code example for calling the Safeguard API for authentication through the standard Safeguard STS login page:

// Browser Example
SafeguardJs.connectRsts('safeguard.sample.corp', `${window.location.protocol}//${window.location.host}${window.location.pathname}`)
.then((connection) => {
    connection.invoke(SafeguardJs.Services.CORE, SafeguardJs.HttpMethods.GET, 'v4/Me')
    .then((results) => {
        console.log(results);
    });
});

For Node.JS, password authentication is available:

// Node.JS Example
SafeguardJs.addCAFromFile('ssl/ca.pem');
let connection = await SafeguardJs.connectPassword('safeguard.sample.corp', 'myuser', 'mypassword');

Password authentication to an external provider is as follows:

// Node.JS Example
SafeguardJs.addCAFromFile('ssl/ca.pem');
let connection = await SafeguardJs.connectPassword('safeguard.sample.corp', 'myuser', 'mypassword', 'myexternalprovider');

Client certificate authentication is also available. This can be done either using a PFX certificate file or a PEM and KEY.

// Node.JS Example
SafeguardJs.addCAFromFile('ssl/ca.pem');
let connection = await SafeguardJs.connectCertificateFromFiles('safeguard.sample.corp', 'ssl/certificateuser.pem', 'ssl/certificateuser.key', null, 'password');

// Node.JS Example
SafeguardJs.addCAFromFile('ssl/ca.pem');
let connection = await SafeguardJs.connectCertificateFromFiles('safeguard.sample.corp', null, null, 'ssl/certificateuser.pfx', 'password');

Client certificate authentication to an external provider is also available. This can again be done either using a PFX certificate file or a PEM and KEY.

// Node.JS Example
SafeguardJs.addCAFromFile('ssl/ca.pem');
SafeguardJs.addCAFromFile('ssl/ca2.pem'); // additional CA for external provider
let connection = await SafeguardJs.connectCertificateFromFiles('safeguard.sample.corp', 'ssl/certificateuser.pem', 'ssl/certificateuser.key', null, 'password', 'myexternalprovider');

// Node.JS Example
SafeguardJs.addCAFromFile('ssl/ca.pem');
SafeguardJs.addCAFromFile('ssl/ca2.pem'); // additional CA for external provider
let connection = await SafeguardJs.connectCertificateFromFiles('safeguard.sample.corp', null, null, 'ssl/certificateuser.pfx', 'password', 'myexternalprovider');

A connection can also be made anonymously

// Browser Example
let connection = SafeguardJs.connectAnonymous('safeguard.sample.corp');

// Node.JS Example
let localStorage = new require('src/LocalStorage').LocalStorage;
SafeguardJs.addCAFromFile('ca.pem');
let connection = SafeguardJs.connectAnonymous('safeguard.sample.corp', null, localStorage);

Authentication is also possible using an existing Safeguard API token:

// Browser Example
let apiToken = GetTokenSomehow();
let connection = SafeguardJs.connectAnonymous('safeguard.sample.corp');
SafeguardJs.Storage.setUserToken(apiToken);

// Node.JS Example
let apiToken = GetTokenSomehow();
let localStorage = new require('src/LocalStorage').LocalStorage;

let connection = SafeguardJs.connectAnonymous('safeguard.sample.corp', null, localStorage);
SafeguardJs.Storage.setUserToken(apiToken);

Two-factor authentication can only be performed through connectRsts(), so that the secure token service can use the browser agent to redirect you to multiple authentication providers.

Most of the examples above use the default SafeguardJs.Storage locations. For RSTS and anonymous connections, SessionStorage is used to persist authentication information. For password and certificate authentication, LocalStorage is used, which is an in memory storage. By writing a new SafeguardJs storage class, these authentication values can be stored elsewhere. Further information can be found here for session storage and here for local storage.

Getting Started With A2A

Once you have configured your A2A registration in Safeguard you can retrieve an A2A password or private key using a certificate and api key.

To retrieve a password via A2A:

// Node.JS Example
SafeguardJs.addCAFromFile('ssl/ca.pem');
let password = await SafeguardJs.a2aGetCredentialFromFiles('safeguard.sample.corp', 'myapikey', SafeguardJs.A2ATypes.PASSWORD, null, 'ssl/certificateuser.pem', 'ssl/certificateuser.key', 'password');

To retrieve a private key via A2A:

// Node.JS Example
SafeguardJs.addCAFromFile('ssl/ca.pem');
let privateKey = await SafeguardJs.a2aGetCredentialFromFiles('safeguard.sample.corp', 'myapikey', SafeguardJs.A2ATypes.PRIVATEKEY, SafeguardJs.SshKeyFormats.OPENSSH, 'ssl/certificateuser.pem', 'ssl/certificateuser.key', 'password');

About the Safeguard API

The Safeguard API is a REST-based Web API. Safeguard API endpoints are called using HTTP operators and JSON (or XML) requests and responses. The Safeguard API is documented using Swagger. You may use Swagger UI to call the API directly or to read the documentation about URLs, parameters, and payloads.

To access the Swagger UI use a browser to navigate to: https://<address>/service/<service>/swagger

• <address> = Safeguard network address
• <service> = Safeguard service to use

The Safeguard API is made up of multiple services: core, appliance, notification, and a2a.

|Service|Description| |-|-| |core|Most product functionality is found here. All cluster-wide operations: access request workflow, asset management, policy management, etc.| |appliance|Appliance specific operations, such as setting IP address, maintenance, backups, support bundles, appliance management| |notification|Anonymous, unauthenticated operations. This service is available even when the appliance isn't fully online| |a2a|Application integration specific operations. Fetching passwords, making access requests on behalf of users, etc.|

Each of these services provides a separate Swagger endpoint.

You may use the Authorize button at the top of the screen to get an API token to call the Safeguard API directly using Swagger.

Examples

Most functionality is in the core service as mentioned above. The notification service provides read-only information for status, etc.

Anonymous Call for Safeguard Status

Sample can be found here.

// Browser Example
SafeguardJs.connectAnonymous('safeguard.sample.corp', saveConnectionCallback)
.then((connection) => { 
    connection.invoke(SafeguardJs.Services.NOTIFICATION, SafeguardJs.HttpMethods.GET, 'v4/Status')
    .then((results) => { 
        console.log(results);
    });
});

Sample can be found here.

// Node.JS Example
let localStorage = new require('src/LocalStorage').LocalStorage;
SafeguardJs.addCAFromFile(caFile);
let connection = await SafeguardJs.connectAnonymous(hostName, null, localStorage);
let result = await connection.invoke(SafeguardJs.Services.NOTIFICATION, SafeguardJs.HttpMethods.GET, 'v4/Status');
console.log(result);

Get remaining access token lifetime

Sample can be found here.

// Node.JS Example
SafeguardJs.addCAFromFile('ssl/ca.pem');
let connection = await SafeguardJs.connectPassword('safeguard.sample.corp', 'myuser', 'mypassword');
let result = await connection.getAccessTokenLifetimeRemaining();
console.log(result);

Register for SignalR events

Sample can be found here.

// Browser Example
function callback(ev) {
    console.log(`Received SignalR event: ${ev.Message}`);
}

SafeguardJs.connectRsts('safeguard.sample.corp', `${window.location.protocol}//${window.location.host}${window.location.pathname}`)
.then((connection) => {
    connection.registerSignalR(logCallback);
});

Sample can be found here.

// Node.JS Example
function callback(ev) {
    console.log(`Received SignalR event: ${ev.Message}`);
}

SafeguardJs.addCAFromFile('ssl/ca.pem');
let connection = await SafeguardJs.connectPassword('safeguard.sample.corp', 'myuser', 'mypassword');
await connection.registerSignalR(callback);

Create a New User and Set the Password

Sample can be found here.

// Browser Example
let user = {
    'PrimaryAuthenticationProviderId': -1,
    'UserName': 'MyNewUser'
};
let password = 'MyNewUser123';

SafeguardJs.connectRsts('safeguard.sample.corp', `${window.location.protocol}//${window.location.host}${window.location.pathname}`)
.then((connection) => {
    connection.invoke(SafeguardJs.Services.CORE, SafeguardJs.HttpMethods.POST, 'v4/Users', user)
    .then((results) => {
        let newUser = JSON.parse(results);
        connection.invoke(SafeguardJs.Services.CORE, SafeguardJs.HttpMethods.PUT, `v4/Users/${newUser.Id}/Password`, `"${password}"`);
    });
});