Getting Started with Sentinel RMS—Connected (Cloud LM) Mode for On-premises Applications

The purpose of this document is to get you started with the license activation and consumption for the Connected (Cloud LM) mode for on-premises applications. This document assumes that you have obtained the:

• Sentinel RMS SDK and SCL Add-on for Sentinel RMS package

•Sentinel EMS instance

•Sentinel Order emails from Thales

Document Organization

This document is organized into the following four parts:

•Part 1: Provides a walkthrough of deploying Cloud LM entitlements.

•Part 2: Describes the generation of registration tokens using Sentinel EMS.

•Part 3: Explains the available options to consume a license.

•Part 4: Explains the steps to view and manage the active sessions.

Key Concepts

Let's review the following concepts and terminology that you need to know to work with Sentinel RMS enforcement in Sentinel EMS.

Concept	Description
Activation	The process of generating and loading licenses on the RMS Cloud License Manager.
Auth Token	Auth token is a concept related to the authentication and authorization of on-premises applications. It contains an access token that is used to authenticate the APIs communicating with RMS Cloud License Manager.
Catalog	A container for all of your Sentinel EMS assets, including products, features, license models, and namespaces.
Customers	Typically, you generate entitlements for a customer who has placed an order. A customer can be an organization that owns an entitlement or a current or potential buyer of an entitlement. A customer can have a single or multiple users.
Enforcement	Licensing technology, such as Sentinel RMS, that controls and secures your software application.
Entitlements	A customer order for one or more products. Similar to orders in your back office system (ERP, CRM, billing system, or sales system), an entitlement can specify the customer that is entitled to use the associated products. Learn More It also includes user details, the products ordered, the features bundled in the products, licensing terms, the number of copies of your product that are available to that customer (quantity), and the entitlement ID (EID). Each entitlement can also be mapped to an actual order or other reference ID in your system using the External ID or Ref ID fields in Sentinel EMS. When an entitlement is ready to be processed, you mark it as complete.
Features	Features are the basic building blocks of products and licenses. Each feature can represent anything from a functional component to an entire application. Learn More This means that you can create separate features for specific functionality, such as "Print" or "Add to Cart", or you can create a feature for each module or for an entire application. After you define at least one feature, you can add that feature to a product. This enables you to sell a product with one or more licensed features. ID. The ID is a unique identifier. During runtime, the Sentinel Licensing API call uses the feature ID. Always ensure that the feature ID is the same in both Sentinel EMS and the Sentinel RMS application you are using to protect your application (Sentinel RMS Envelope or Sentinel Licensing API).
License Model	License Model is the building block that defines the deployment mode and the license properties depending on your product marketing strategies.
Namespace	A namespace acts as a logical partition for your Sentinel EMS workspace. If you have multiple product lines, you can maintain different namespaces for them. The features, products, and product suites defined in a namespace are available only to those users who have permissions for that namespace. Users with roles that have entitlement-related permissions (such as order takers) can access these items from all namespaces.
Products	A product represents a saleable item in your organization—such as a software application—usually with a SKU or similar unit. You can package products with individual features.
Registration Token	Registration token is a concept related to authentication and authorization of on-premises applications. It is a bootstrap token that enables licensed applications to get their individual auth tokens and consume RMS Cloud License Manager REST API. Registration Token is required in either scenario, whether you are licensing applications using the SCP-integrated library or Cloud License Manager (LM) REST API.
RMS Cloud License Manager	Multi-tenant cloud-based Sentinel RMS License Manager (LM) for cloud licensing and usage collection.
User (Standard Type)	A user is an individual who serves as the single point of communication for an entitlement. You create users for customers and then generate entitlements for them. All emails related to an entitlement are sent to the specified user.
User (Administrator Type)	A customer user with higher privileges who can also generate registration tokens, manage auth tokens, and/or terminate active end user sessions using the Customer Portal. This may be required in the scenarios when software vendor allows customers to perform activations and manage license sessions on their end instead of the vendor managing them.