Sentinel RMS Enforcement - License Models

Sentinel EMS supports Sentinel RMS as the default enforcement technology. Sentinel Cloud licensing (SCL) is an add-on for Sentinel RMS and is used in conjunction with Sentinel EMS to support leased and cloud served licenses. Sentinel EMS can be used with or without the SCL Add-on for RMS.

This section lists the Sentinel RMS license models and attributes supported in Sentinel EMS. The attributes are listed in order of their groups. The default values for the attributes are provided in a separate column. For more details on the meaning and usage of these license models and attributes refer to the Sentinel RMS Documentation provided with the Sentinel RMS SDK.

NOTE   Sentinel RMS 8.5.0 and above provides support for the "Aggregate" license model. In Sentinel EMS, this requires setting the value of the attribute Enforce License Exclusive to "Aggregate".

Permissions

For user and end user Permissions, the values in the table have the following meanings:

>None: These attributes are displayed while defining license models. These are not displayed while copying a license model, activating the product, or accessing the Entitlement page. These values are fixed and cannot be changed once a license model is defined.

>Read: These attributes are displayed, but the user cannot change them (e.g., lock criteria).

>Write: These attributes require user input.

Attribute Groups

Sentinel RMS license models may contain some or all of the following attribute groups:

Attribute Group	Description
License Duration	Duration for which the license is valid.
Limits	Usage restrictions, such as the maximum number of users (User Limit) and the user threshold for generating alerts (Soft User Limit).
Network Term	Time and sharing-related attributes, such as grace period, sharing criteria, checkout period, and commuting licenses.
Policy	Policy features in a license, such as time tampering, token sharing, and license detachment.
Locking	Locking attributes of a license, for example, Number of User Nodes and Primary 1 Criteria.
Vendor	Miscellaneous information that you can include for identification as a part of your license code.
Cloud Served	Deployment details such as, deployment type for lease, duration, and sync frequency.
Capacity	Capacity details for pooled and non-pooled license models, such as the capacity limit.