License Models with Sentinel RMS SDK
The table below lists the License Models supported by the Sentinel RMS SDK and Sentinel EMS. For a comparative snapshot of the attributes supported by each license model, see Sentinel RMS SDK License Models and Their Attributes.
| License Model | Description |
|---|---|
| Auto Checkout |
Use for generating a Sentinel RMS license with the following major characteristics: >Network: Generates a floating license. The default network user limit is set as 100. The option to set the token sharing and holding are also allowed. >Node-locked: The license is locked to a particular computer and cannot be used by any other system. In addition, the license works like the repository license of Sentinel RMS. Unlike a commuter license, repository license does not require manual specification of checkout days/hours. NOTE Thales recommends using CustomEx when a software vendor needs to check out a network license on a client device that does not support the standard fingerprint. |
| Commuter |
Use for generating a Sentinel RMS license with the following major characteristics: >Network: Generates a floating license. The default network user limit is set as 100. The option to set the token sharing and holding are also allowed. >Node-locked: The license is locked to a particular computer and cannot be used by any other system. In addition, this license allows manual commuting of license token from the License Manager for a period (specified as checkout days). NOTE Thales recommends using CustomEx when a software vendor needs to check out a network license on a client device that does not support the standard fingerprint. |
| Network Node Locked |
Use for generating a Sentinel RMS license with the following major characteristics: >Network: Generates a floating license. The default network user limit is set as 100. The option to set the token sharing and holding are also allowed. >Node-locked: The license is locked to a particular computer and cannot be used by any other system. |
| Non-Pooled Capacity Node Locked |
Use for generating a Sentinel RMS license with the following major characteristics: >Network: Generates a floating license. The default network user limit is set as 100. The option to set the token sharing and holding are also allowed. >Node-locked: The license is locked to a particular computer and cannot be used by any other system. In addition, each team works within the specified capacity limits and allows sharing of capacity within that team only. |
| Pooled Capacity Node Locked |
Use for generating a Sentinel RMS license with the following major characteristics: >Network: Generates a floating license. The default network user limit is set as 100. The option to set the token sharing and holding are also allowed. >Node-locked: The license is locked to a particular computer and cannot be used by any other system. In addition, this license allows sharing of capacity across all teams. Any team can request and obtain out of total pool till the request can be fulfilled from remaining capacity. |
| Redundant Node Locked |
Use for generating a Sentinel RMS license with the following major characteristics: >Network: Generates a floating license. The default network user limit is set as 100. The option to set the token sharing and holding are also allowed. >Node-locked: The license is locked to a particular computer and cannot be used by any other system. In addition, the license allows setting the License Manager redundancy fields such as: >Enforce redundancy >The number of servers (License Managers) >Allows locking information of various (up to 11) License Managers |
| Standalone Node Locked |
Use for generating a Sentinel RMS license with the following major characteristics: >Standalone: The licensed software and the license file are installed on the computer. >Node-locked: The license is locked to a particular computer and cannot be used by any other system. |
| Subscription |
Use for generating a Sentinel RMS license with the following major characteristics: >You can specify an end date in terms of number of days. >Network: Generates a floating license. The default network user limit is set as 100. The option to set the token sharing and holding are also allowed. >Node-locked: The license is locked to a particular computer and cannot be used by any other system. So, apart from the client-locking information (user node criteria and information), locking information of the License manager system (primary and secondary) are also introduced. |
| Trial Network |
Use for generating a Sentinel RMS license with the following major characteristics: >Trial: Allowing licensed software use for fixed days or hours starting from the first use. >Network: Generates a floating license. The default network user limit is set as 100. The option to set the token sharing and holding are also allowed. Note that a trial license cannot have grace period associated. >Unlocked license: The license generated is not locked to any particular computer and can be used on any other system. |
| Trial Network Node Locked |
Use for generating a Sentinel RMS license with the following major characteristics: >Trial: Allowing licensed software use for fixed days or hours starting from the first use. >Network: The license generated will not be a standalone or repository license. The default network user limit is set as 100. The option to set the token sharing and holding are also allowed. Note that a trial license cannot have grace period associated. >Node-locked: The license is locked to a particular computer and cannot be used by any other system. So, apart from the client-locking information (user node criteria and information), locking information of the License manager system (primary and secondary) are also introduced. |
| Trial Standalone |
Use for generating a Sentinel RMS license with the following major characteristics: >Trial: Allowing licensed software use for fixed days or hours starting from the first use. >Standalone: The licensed software and the license file are installed on the computer. >Unlocked license: The license generated is not locked to any particular computer and can be used on any other system. |
| Trial Standalone Node Locked |
Use for generating a Sentinel RMS license with the following major characteristics: >Trial: Allowing licensed software use for fixed days or hours starting from the first use. >Standalone: The licensed software and the license file are installed on the computer. >Node-locked: The license is locked to a particular computer and cannot be used by any other system. |
Sentinel RMS SDK License Models and Their Attributes
The table below lists the attributes contained in each License Models available with the Sentinel RMS SDK:
| Attribute Groups and Name | Description | Default Value | Optional | Auto Checkout | Commuter | Network Node Locked | Non-Pooled Capacity Node Locked | Pooled Capacity Node Locked | Redundant Node Locked | Standalone Node Locked | Subscription | Trial Network | Trial Network Node Locked | Trial Standalone | Trial Standalone Node Locked | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Define Attributes | ||||||||||||||||
| License Version | Specifies the license version. | 23 - RMS 10.2 | No |
|
|
|
|
|
|
|
|
|
|
|
|
|
| License Duration | ||||||||||||||||
| Start From Activation Date |
License start date will start on the day of the activation. |
No | No |
|
|
|
|
|
|
|
|
|||||
| Start Date |
The date (day, month, and year) before which the licensed software cannot be run.
A No start date checkbox can be used to exclude the start date. This option can be selected for licenses so that embedded devices that do not have system clock can be supported. |
01/01/2024 12:00 AM | No |
|
|
|
|
|
|
|
|
|
|
|
||
| End Date |
The date (day, month, and year) beyond which the licensed software cannot be run.
A Never expires checkbox can be used to indefinitely extend the end date. |
01/01/2024 12:00 AM | No |
|
|
|
|
|
|
|
|
|
|
|
||
| License Duration (in days) |
Duration of license in days. |
365 | No |
|
||||||||||||
| Limits | ||||||||||||||||
| User Limit |
Limit that sets the maximum number of users that can run the licensed software. Maximum Value: 4294967294 if license version is 20 and 10000000 for license version 19. |
100 | No |
|
|
|
|
|
|
|
|
|
|
|
|
|
| Soft User Limit | A sub-limit lesser than user limit that is set to generate alerts. | Unlimited | No |
|
|
|
|
|
|
|
|
|
|
|
|
|
| Key Lifetime (min) | Refers to a unit of time specified for the license to send updates to the license manager. | 5 minutes | No |
|
|
|
|
|
|
|
|
|
|
|
|
|
| Trial Duration Days |
The number of days for which the trial license is valid. NOTE Trial Duration Days cannot be updated for an entitlement that is marked as completed. |
30 | No |
|
|
|
|
|||||||||
| Trial Duration Hours | The number of hours for which the trial license is valid. | 0 | No |
|
|
|
|
|||||||||
| Network Term | ||||||||||||||||
| Grace Period | Specify whether or not grace period is allowed. | Disallowed | No |
|
|
|
|
|||||||||
| Grace Period (days) | Specifies the number of days of grace. | 0 | No |
|
|
|
|
|||||||||
| Grace Period (elapsed hours) | Hours elapsed from the grace period specified. | 0 | No |
|
|
|
|
|||||||||
| Maximum Checkout (days) |
Specifies the maximum number of days a commuter license can be checked-out for. NOTE Maximum Checkout (days) cannot be updated for an entitlement that is marked as completed. |
30 | No |
|
||||||||||||
| Sharing Criteria | Determines whether license sharing is allowed for the feature or not. | No Sharing | No |
|
|
|
|
|
|
|
|
|||||
| Sharing Limit | Specifies the number of licenses available for sharing. | 0 | No |
|
|
|
|
|
|
|
|
|||||
| License Holding Criteria |
Specifies the license holding criteria as: >License Specified >Application Specified OR >No Hold Time |
No Hold Time | No |
|
|
|
|
|
|
|||||||
| Key Holdtime (min) | A network license may be held for some time after it is released by a specific user. The license manager holds the license for the hold time minutes specified. | 0 | No |
|
|
|
|
|
|
|||||||
| Policy | ||||||||||||||||
| Output Type | Determines the format of the license generated. | Encrypted | No |
|
|
|
|
|
|
|
|
|
|
|
|
|
| Enforce License Exclusive | Enforce that an exclusive license code completely replaces the old license with a new license. | Exclusive | No |
|
|
|
|
|
|
|
|
|
|
|
|
|
| Enforce Clock Tampered | Software licensing may break down if the customer sets back the system time to prevent license expiration. The attribute "Enforce Clock Tampered" detects system clock tampering. | Yes | No |
|
|
|
|
|
|
|
|
|
|
|
|
|
| VM Detection | Enforce a policy through the license to deny or allow application usage on VM. | Disabled | No |
|
|
|
|
|
|
|
|
|
|
|
|
|
| Log Encryption Level | Specifies the encryption level of the usage log file (created on the License manager end for network licenses). | End User Defined | No |
|
|
|
|
|
|
|
|
|
||||
| Allow Redundancy | License allows License manager redundancy | True | Yes |
|
||||||||||||
| Enforce Majority Rule | Specifies that majority of redundant License managers must be running. If the number of redundant License managers running is less than half of the number of License managers specified in the license file, then all License managers will stop servicing all old and new clients. | True | No |
|
||||||||||||
| Capacity | ||||||||||||||||
| Capacity | Specifies the capacity limit for the license. | No Limit | No |
|
|
|||||||||||
| Capacity Flag | Specifies whether the license capacity is allowed. | Non-Pooled capacity | Yes |
|
|
|||||||||||
| Locking | ||||||||||||||||
| Number of User Nodes | Number of user nodes | 0 | No |
|
|
|
|
|
|
|
|
|||||
| Primary 1 Criteria | The primary locking criteria for a client, for node-locked licensing. | Disk ID | No |
|
|
|
|
|
|
|
||||||
| Secondary 1 Criteria | The secondary locking criteria for a client, for node-locked licensing | - | Yes |
|
|
|
|
|
|
|||||||
| Primary 2 criteria (in hex) | The primary 2 locking criteria for a client, for node-locked licensing | Disk ID | No |
|
||||||||||||
| Primary 3 criteria (in hex) | The primary 3 locking criteria for a client, for node-locked licensing | Disk ID | No |
|
||||||||||||
| Num Servers | Number of license servers available to support redundancy. | 3 | Yes |
|
||||||||||||
| Num client locked | Number of client-locked licenses. | 1 | No |
|
|
|||||||||||
| Client 1 criteria (in hex) | The primary locking criteria for a client, for node-locked licensing. | Disk ID | No |
|
|
|||||||||||
| Vendor | ||||||||||||||||
| Private Information |
Additional information that you can include as part of your license code for identification. The private vendor information remains encrypted. |
Yes |
|
|
|
|
|
|
|
|
|
|
|
|
||
| Public Information |
Additional information that you can include as part of your license code for identification. The public vendor information remains encrypted in encrypted licenses and readable in readable licenses. |
Yes |
|
|
|
|
|
|
|
|
|
|
|
|
||
| Comments |
Vendor comments. Maximum: 150 characters NOTE This field cannot be read or parsed by Sentinel RMS. |
- | Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
| Number of Secrets | Specifies the total number of secrets for the challenge-response mechanism (A technique used for authenticating the License manager). The maximum number of secrets that can be specified is seven. | 0 | No |
|
|
|
|
|
|
|
|
|
|
|
|
|
| License Vendor Information |
Additional information about the vendor that you can include as part of the license code for identification. License vendor information remains encrypted in all types of licenses (readable or encrypted). If the license string is decoded, the encrypted information becomes readable. |
No |
|
|
|
|
|
|
|
|
|
|
|
|
||