Implementing Cloud Licensing

NOTE   Sentinel LDK Cloud Licensing requires a paid subscription for the Cloud Licensing module. Although SL and HL keys with concurrency may technically be used over the cloud in some cases with some configurations, this is not by design, and Thales cannot guarantee acceptable security or reliability for such a setup. The only supported configurations for cloud licensing in Sentinel LDK require the paid module and the integration of machine accounts or user-based licensing.

This section describes how to implement cloud licensing in Sentinel LDK.

Cloud licensing can be implemented using one of the following methods:

>User-based licensing using OAuth authentication

User-based licensing uses OAuth to enable end users to access the vendor's application or service using login credentials—their user name or email address and their password. End users can log in to the application from any supported device without the need to activate a license or install anything special on the device. With user-based licensing, the user is authorized instead of the device.

For more information, see Sentinel EMS User Guide for Sentinel LDK.

>Using machine accounts

Machine accounts are used to manage identity strings. The cloud licensing service is hosted on Thales' servers. For more information, see Sentinel EMS User Guide for Sentinel LDK.

>Using Sentinel Admin Control Center

Using Sentinel Admin Control Center to manage licensed users is described in the following topics:

In this section:

Cloud Licensing (Using Sentinel Admin Control Center) – Overview

Vendor-Hosted Implementation Summary

Setting Up the License Server Machine

Installing a Client Identity on an End User's Machine

Customer-Hosted Implementation Summary

Cloud Licensing Performance

Overview for Multi-Level License Servers

Online Detach: Setting Up Multi-Level License Server Machines

Offline Detach: Setting Up Multi-Level License Server Machines

Configuring High Availability for Cloud Licensing