Glossary
Refers to the generation of a license code or file for a product |
||
Activation ID (AID) | Refers to the unique identifier for an activation. | |
Admin | Refers to the default user in Sentinel EMS. The Admin is a super user (with all permissions in Sentinel EMS) and can managing access rights of other users. His primary responsibilities are managing users, roles, namespaces, custom reports, templates, and file import. | |
Allow Grace | The grace time period allows running the network application for a limited period (days/hours) even when the network is not accessible. It provides the convenience of using the application under unprepared circumstances, such as enterprise network break-down or when users are at home. | |
Allow VM detection | Specifies if the license tokens will be issued if the License Manager is found running on a virtual machine. | |
Auto-checkout |
Refers to the Repository license model of Sentinel RMS, which has the following characteristics: >Network license: Concurrent user licenses or "floating" licenses for users in a network. Anyone on the network can use the application. The number of users can be up to the limit specified in the license file. >Automatically commutable: Means that the licensed application can run on the local system even beyond network because it can be automatically commuted (without requiring a formal checking out process). |
|
|
Authentication profile | Associated with webhooks to control how client applications are authenticated. |
Also known as Namespace |
In Sentinel EMS, a Sentinel LDK batch code is known as a namespace. A batch code (or namespace) represents your company's unique vendor code. When you order Sentinel protection keys from Thales, you specify your batch code, which is both written to the keys before dispatch and printed on the outside of each Sentinel HL key. Your company can have one or more batch codes. The batch code for Sentinel protection keys with a demo vendor code is DEMOMA. |
|
|
Batch Entitlement or “in batch” | Refers to the generation of multiple entitlements at one go. Batch entitlements enable software vendors to create large batches of products so that the entitlement IDs can be printed right on the box and sold through various channels without knowing the end user. |
|
Batch ID | Refers to the unique identifier corresponding to multiple entitlements generated in a batch. |
|
||
Billing address | Billing address is the address registered on your credit card. In simple words, it is the address where you receive the statements for your credit card. For your order to be approved when shopping online, the billing address provided by you has to match this address. | |
C2V file | Customer-to-Vendor file. A file that is sent by the customer to the vendor prior to activating a product. The file may contain data about the customer's computer for identification purposes and/or license information. C2V files do not contain private customer information and can safely be sent by email. | |
Catalog | Refers to the namespaces, features, license models, |
|
Catalog Permissions | Permissions for viewing, editing, adding, and deleting features, |
|
Challenge Response Secrets | Challenge-response mechanism is a technique used by the vendor for authenticating Sentinel RMS License Manager so that imposter license managers do not intercept and handle client communication. The challenge strings (secrets) defined are encrypted within the license code, with only the License Manager knowing how to decrypt them. The License Manager will then compute an authentication response when challenged by a client to confirm its identity. Up to seven secret text strings can be specified, each up to twelve characters long. "!" and "$" are reserved characters and cannot be used with secret text. "#" is a comment character and any text appearing after this symbol will be ignored. | |
Channel Partner | Refers to an organization that is allowed to re-sell the software vendors products. End users can buy directly from software vendors or from the channel partners. | |
Channel Partner User | Refers to an individual user who belongs to a channel partner. Such users can manage the entitlements associated with their channel partner. | |
Cloud Licensing Permissions |
Refer to the permissions that enable a customer's end users to access protected applications on CL keys. Relevant only for service-hosted cloud licensing on a Thales service-hosted, cloud license manager server. See also: |
|
Cloud Licensing Server |
Refers to the Thales service-hosted, cloud license manager server that manages CL keys. See also: Machine Accounts |
|
Commit Entitlement | After an entitlement is created and every Line Item is configured, the entitlement can be committed. Committing an entitlement freezes the entitlement from further changes, and emails a copy of the entitlement certificate (if so configured) to the end user (if specified). | |
|
Commuter |
A Sentinel RMS license model. Useful when a user needs to travel and wants to take along the licensed application. A network license can be used as a commuter license. Commuter licenses differ from Auto-checkout, because commuter licenses must always be manually checked out from the network before use. |
Complete state |
In this state, a product |
|
Compliance | Refers to conforming the terms and conditions of the end user license agreement (EULA). | |
Contact |
See User. |
|
Copy Product |
A new product |
|
Custom Attribute | Refers to the custom attributes that can be created under the Template menu. | |
Custom Reports | Help the software vendor to generate customized reports (in addition to the predefined reports). | |
Customer | Refers to the organization that owns an entitlement. A customer can have multiple users. | |
Deployed | A product |
|
(Previously known as Deployment Type) |
Specifies whether your licensed application will be hosted on the cloud or will be installed locally, as well as other deployment criteria. For information, see the section on deployment modes in Sentinel RMS Developer Guide. |
|
Draft state (for an entitlement) |
When an entitlement is first created, it remains in draft state. In this state the entitlement can be edited and each Line Item can be configured. Draft entitlements cannot be viewed or activated by the end user or channel partner. | |
Draft state (for a product |
When a product |
|
Electronic Software Delivery (ESD) | Delivering software packages and updates via the Internet as opposed to the shipping of physical media such as CDs, DVDs, and flash drives. | |
End Date (for an entitlement line item) |
The date after which no operations, such as login by product key NOTE As one line item can have multiple licenses for multiple features, specifying a license end date different from the line item end date helps in addressing different end dates for multiple features. |
|
End Date (for an entitlement) |
The date after which operations, such as login by EID |
|
End User | Refers to the ultimate user of the products |
|
End-of-Life or EOL state | When a product is no longer in use, its state can be changed to End of Life (EOL). In this state the product |
|
Enforce Clock Tampered |
Software licensing may break down if the customer sets back the system time inadvertently, such as, to prevent the license expiration. This term is provided as a check box option in the Sentinel EMS portal. Selecting or clearing this check box specifies if the software vendor wants to deny or allow the use of the licensed application in case of system clock tampering. |
|
Enforce License Additive |
An additive license code appends changes to an existing additive license. Whereas, an exclusive license code completely replaces the old license with a new license. |
|
Enforce License Exclusive | ||
Enforcement | The licensing technology that controls and secures the software vendor's application, such as Sentinel RMS |
|
Entitlement | Refers to the rights of an end user to use a software package. An entitlement includes information such as who can use it and for what duration. An end user can activate an entitlement to generate a license to use the software conforming to the defined terms. | |
Entitlement Lifecycle | Refers to the series of changes in the state of an entitlement, from creation and activation through upgrading, renewing, and revoking. | |
Feature | A feature is a distinct functionality of a software application that can be independently licensed. Features are the basic building blocks of a product. | |
Fulfillment | The complete process through which the customer gets the product and license. | |
Global Permissions | Refers to the general permissions in Sentinel EMS such as view, edit, add, delete. These permissions define the rights to use various functionalities in Sentinel EMS. | |
Identity Code |
A unique, read-only, 7-character string. An identity code is part of the full identity string that specifies the client identity for the machine account as defined in the Thales service-hosted, cloud license manager server database. Used with a machine account. See also: Machine Accounts |
|
Identity Link / Identity String |
An identity link contains the identity string that identifies an end user that accesses licenses for protected applications from the Thales service-hosted, cloud license manager server. An end user installs the identity string on the client machine by clicking the identity link supplied by the customer. This enables the machine to communicate with the license manager server. Example of identity string: FFSTQYU:oBWAAQCBEFPxvWKzIBicixs/v0rerEA@licenseserver.example.com Example of identity link: https://cloudportal.example.com/_int_/install.html?identity=FFSTQYU:oBWAAQCBEFPxvWKzIBicixs/v0rerEA@licenseserver.example.com See also: Machine Accounts |
|
Key Lifetime Minutes |
After an application obtains a license, it also faces the task of maintaining the license. A license must be renewed by the application on a regular schedule or the license will be reclaimed (keeping it booked so that new clients do not obtain it). This is managed by sending an update call to the license server that issued the license. So, lifetime in minutes refers to the time interval specified for the license (key) to send updates to the license server. |
|
License | A file or string generated by the software vendor that contains the conditions under which the software can run on the customer’s machine. License is the final outcome of an entitlement. | |
License Duration |
The fixed calendar dates beyond which the licensed application cannot be used. |
|
License Generators | Refers to the software that generates license codes or files that are distributed by Sentinel EMS. Sentinel EMS is fully integrated with the Sentinel RMS license generator and also supports third-party license generators. | |
License Model | A license model is a combination of various parameters that define the type of license to be generated. License models define a broad category of licenses that can be further customized by editing their attribute values. License models can be included with features. | |
License Version |
The license version associated with a Sentinel RMS license. The license version maps to the SDK version in which the license was introduced. If a new feature or license property is introduced in the SDK, then the license version will be upgraded as the new feature would not be available with earlier SDKs. For example, grace licenses were introduced in SDK v8.0.x and cannot be generated with earlier SDKs. |
|
Line Item | A product |
|
Lock Code / Locking Code / Fingerprints | Refers to the actual output string (in hex format) resulting from locking to the system properties. | |
Refers to binding a license to particular system properties, such as, the hard drive, IP address, and CPU properties. | ||
Machine Account |
Created for a customer's end user, a machine account represents a set of cloud licensing permissions that grant authorization rights to access protected applications. Machine accounts are an integral part of cloud licensing (also known as CL). See also: Machine Accounts |
|
Market Group | A market group provides an added layer of access control that enables you to increase the operational efficiency of Sentinel EMS by segregating data access according to geographical location or business unit. | |
Memory file | A memory file is a data file that is used for storing strings in a Sentinel key. Usage examples might include migrating existing license data to Sentinel EMS, storing homegrown license data, or usage counters. | |
(for all enforcements except for Sentinel LDK ) |
A namespace acts as a logical partition for your Sentinel EMS workspace, providing unique storage locations within Sentinel EMS. If you have multiple product lines, you can maintain different namespaces for them. The features |
|
(for Sentinel LDK) Also known as Batch Code |
A Sentinel EMS namespace is known as a batch code in Sentinel LDK. A namespace (batch code) represents your company's unique vendor code. When you order Sentinel protection keys from Thales, you specify your namespace, which is both written to the keys before dispatch and printed on the outside of each Sentinel HL key. Your company can have one or more namespaces. The namespace for Sentinel protection keys with a demo vendor code is DEMOMA. In Sentinel EMS, a namespace also acts as a workspace, differentiating between separate storage locations |
|
Network | A type of license (in contrast with a standalone license). Described above in Auto-checkout. | |
Network User Limit |
The maximum number of users a network license can support concurrently. |
|
Node Locked | Described below (see Trial Standalone Node Locked). | |
Output Type |
Refers to the format of generated RMS licenses, such as, encrypted and readable. |
|
Permissions |
Permissions define different levels of access to use various functionalities of Sentinel EMS. Permissions are not assigned to users directly, but are grouped into roles, and users can be assigned roles. See also: Role |
|
Primary Criteria and Secondary Criteria |
For server-locked licenses, you can specify two sets of locking criteria known as primary and secondary locking criteria. The licensed application will run if any of the locking criteria is matched. |
|
Private Vendor Info | See Vendor Info below. | |
Product | A product is a software application that can be ordered or licensed. It is a combination of individual features and is associated with one or more license models. | |
Product Family |
Group of products derived from a common product platform. These goods or services use similar or same production processes, have similar physical characteristics, and may share customer segments, distribution channels, pricing methods, promotional campaigns, and other elements of the marketing mix. Products comprising a family are usually priced and discounted as a package. Several product families make up a product portfolio.
|
|
Product Key | A unique string that identifies a Line Item in an entitlement. Product keys can be used to log in and activate the relevant line item. Every product key is unique across entitlements. | |
Product Suite | A product suite* is a combination of products that are meant to be sold together. The products included in a product suite* may be functionally similar or complementary. A product suite* can include one or more products from its parent namespace. | |
Public Vendor Info | See Vendor Info. | |
Publisher | Refers to the organization who may be a or a hardware manufacturer, who wants to protect his products using software license or hardware key and manage entitlements for them. | |
Quantity |
Each product > For Standalone Sentinel RMS licenses, quantity always refers to Number of Activations. For each feature the order taker can specify a User limit. > For Network Sentinel RMS licenses, you may specify whether Quantity refers to Number of Activations or Seat Count (maximum concurrent users). For Network licenses: > If Quantity is used as Number of Activations, for each feature the order taker can specify user limit (number of seats). During activation, the feature will have fixed Seat Count as defined by the order taker. > If Quantity is used as Seat Count, the order taker is not required to specify a different seat count for each feature. During activation the end user needs to specify activation quantity, which is used as Seat Count for each feature. |
|
Registered Machine |
A client device that accesses licenses for protected applications from the Thales service-hosted, cloud license manager server. Used with a machine account. See also: Machine Accounts |
|
Regular Expression |
A regular expression can be specified for an attribute in a template to define some restrictions for the input type of the attribute. Example of a Regular expression is [-a-z0-9]+(\.[-a-z0-9]+)* |
|
Reports | Sentinel EMS reports provide access to selected current information from the Sentinel EMS database. Different predefined reports are available to meet various requirements. The reports provide information in tabular form and, where applicable, in a graphical chart. | |
Revocation or License Revocation |
Revocation is a process by which a software vendor allows return of licenses by the customer. NOTE Third-party licenses can be revoked using the Revoke Immediately option. |
|
Revocation Tool – command-line based | A command-line tool that software vendors can use to configure license revocation on end users' computer. | |
Revocation Tool – GUI based | A GUI-based tool that software vendors can use to configure license revocation on end users' computer. | |
Role |
A set of permissions that can be linked with users to manage their access rights. See also: Permissions |
|
Run-time Environment (RTE) |
System component that enables communication between a Sentinel protection key and a protected application or data file. The Run-time Environment also contains Sentinel Admin Control Center. |
|
Sentinel HL key |
The hardware-based protection and licensing component of Sentinel—a physical Sentinel HL key (such as a dongle). >Sentinel HL Basic key. Standard Sentinel HL local key that is used to protect software, and has a perpetual license. This key: •Does not have any memory functionality. •Does not support concurrency or remote desktops. •Does not support V‑Clock. >Sentinel HL network key. Any Sentinel HL key that supports concurrency. This includes the following keys: •Sentinel HL Net key •Sentinel HL NetTime key •Any Sentinel HL (Driverless configuration) key except for Sentinel HL Basic keys >Sentinel HL (Driverless configuration) key Sentinel HL key that does not require the Run-time Environment to protect an application or data file on a Windows machine. >Sentinel HL (HASP configuration) key. Sentinel HL key that is fully compatible with protected applications that require the older HASP HL keys. For more information about Sentinel HL keys, see Sentinel LDK Software Licensing and Protection Guide and Sentinel Hardware Protection Keys. |
|
Sentinel LDK Cloud Licensing (CL) | Thales-hosted cloud licensing service that enables your customers' end users to consume licenses anywhere, anytime, from any machine, without the need for performing activation or storing licenses locally. | |
Sentinel SL key |
The software-based protection and licensing component of Sentinel—a virtual Sentinel HL key. Product activation is instantaneous. End users can immediately start using the software with its fully-licensed functionality. The online connection with end users can enable user registration data to be collected and used for marketing purposes. |
|
Shipping address | The address where you want to receive your orders is called the Shipping Address. It could be your home or office. | |
Standalone |
A type of license that is intended for single computers. |
|
The date before which no operations, such as login by product key NOTE As one line item can have multiple licenses for multiple features, specifying a license start date different from the line item start date helps in addressing different start dates for multiple features. |
||
Start Date (for an entitlement) |
The date before which operations, such as login by EID |
|
State of a Product |
The different states of a product |
|
Template | A template is a set of custom attributes that create placeholders to store or input additional information for features, products |
|
Test Entitlement |
A test entitlement lets you make sure that the products, features, and license models are defined in an appropriate manner before deploying them to production. The process of generating a test entitlement is similar to that of a normal entitlement. However you can create a test entitlement using products You can activate and revoke test entitlements, but their data is excluded from Reports. |
|
Trial duration |
The time period (defined in the number of days or hours) to allow the use of the licensed application. |
|
Trial Standalone Node Locked |
A Sentinel RMS license model, which is all of the following: >Trial: A temporary license that allows software usage for fixed days or hours starting from the first use. >Standalone: A license typically meant for non-networked environments (such as home users). >Node locked: Means the software can only be used on one machine. |
|
User |
Either an end user, or a user in the customer organization that manages entitlements for end users in that organization. A user can receive email notifications about entitlements, activations, and so on. A user often activates entitlements in the Sentinel EMS customer portal. For retail customers, it is suitable to create users and generate entitlements for them. Also known as contact. |
|
User ID or User Name | A unique identifier for a user in Sentinel EMS. | |
User Limit |
> For Network Licenses: Specifies the number of tokens (concurrent instances) a license can have. > For Standalone Licenses: Setting a user limit for standalone licenses will limit the number of licensed features used concurrently. For example, a customer purchased a licensed application, which has five features licensed and hard limit is set to three. This limit will ensure that not more than three licensed features are used concurrently. However, since standalone licenses can be used by any number of local applications (instances), the hard limit set may not hold much meaning, especially in desktop environments. This is useful for platforms where the whole operating system is treated as a single application and, therefore, all tasks and processes share memory space. In such environments, the user limit can be used with standalone licenses for controlling the features of a device. > The maximum number of users that can run the licensed software. The administrator can set the User Limit Configuration attribute in the Sentinel EMS Administration Console to regulate the usage of the component multiplier and the license model user limit. |
|
User registration | The process by which the end user provides general information when logging on to the Sentinel EMS customer portal for the first time. For more information, see Guide to the Sentinel EMS Customer Portal . | |
V2CP file |
Vendor-to-Customer package file. A file that contains license information for an activated product. The V2CP file is available for download at the end of the activation process. For offline activations, the vendor or end user (customer) uses the V2CP file to apply the encoded license on the relevant computer. V2CP files can safely be sent by email. You can customize the V2CP file name format, if needed. For details, see License File Name (V2CP) Configuration. |
|
Vendor comments | Refers to comments that can be specified by the software vendor to be appended at the end of a Sentinel RMS license. | |
Vendor Info |
Refers to additional information that a software vendor can include as a part of the license code for identification. The private vendor information will remain encrypted in all license formats (whether readable or encrypted). The public vendor information will remain encrypted in encrypted licenses and readable in readable licenses, respectively. |
|
Vendor User | Refers to the employee of the software vendor who is responsible for performing various entitlement-related tasks in Sentinel EMS. | |
Version |
Versions can be defined when creating features NOTE This is different from license version. |
|
Virtual Clock | Virtual clock that is available in Sentinel SL keys and Sentinel HL (Driverless configuration) keys. In Sentinel LDK, also known as V-Clock. | |
|
Webhook | Notifies client applications about an update to a Sentinel EMS entity. |