Implementation Summary

The following steps summarize the process of implementing the cloud licensing model.

1.Set up a global license server that allows access to licenses via the Internet. For details, see Setting Up the License Server Machine.

2.Deploy Sentinel LDK Cloud Portal in the same environment. For more information, see Sentinel LDK Installation Guide.

3.In Sentinel LDK-EMS Configuration Guide, see the description of the URL for Cloud Portal parameter and ensure that you comply with all the requirements.

4. Log in to Sentinel LDK Cloud Portal using the credentials set during deployment and modify the configuration parameters as required. For more information, see Sentinel LDK Cloud Portal Guide for Vendors .

5.Protect your applications using Sentinel LDK. Ensure that the Locking Type includes the option to use SL AdminMode keys.

6.Use Sentinel LDK-EMS to generate a separate CL key for each customer organization, using the Produce & Push option to deliver entitlements.

The license must allow concurrency. Specify the required number of network seats.

7.For each customer organization defined in Sentinel LDK-EMS, use Sentinel LDK-EMS to define one or more contacts. Each contact can serve as a customer administrator in Sentinel Cloud Portal to define and manage licensed users within their organization.

Using Sentinel Cloud Portal, send each contact an email with credentials that enable the contact to log in to Sentinel Cloud Portal as a customer administrator and perform administrative tasks for users in their organization. For more information, see Sentinel LDK Cloud Portal Guide for Customers.

8.The customer administrators log in to Sentinel Cloud Portal and define licensed users in their organization.

NOTE   The vendor has the option of defining and managing licensed users directly in Sentinel LDK Cloud Portal without defining customer administrators.

9.The customer administrators can configure the client identity for each licensed user to allow access to one or more product licenses on the license server. Each client identity can also be configured with additional options depending on global parameters configured by the vendor.

10.Sentinel Cloud Portal sends each licensed user an email with a link that allows the user to easily install the identity string on their machine.

NOTE   To use the provided link, Sentinel LDK Run-time Environment must be present on the user's machine. Sentinel Run-time Environment can be installed together with the protected application. If installing Sentinel LDK Run-time Environment is not possible, you can send the identity string to the user as a text string, with instruction on how to install the string manually. For details, see Installing a Client Identity on an End User's Machine.

11.The end user installs the relevant protected application. The user can register their identity string on multiple machines (up to the limit you specify).

12.The end user proceeds to execute the protected application. The application consumes a network seat from the vendor's license server machine.
OR
The end user detaches a network seat from the license server machine to the local machine. The user can then proceed to execute the protected application offline.