License Properties Supported with Grace Licenses
A grace license is a network license that supports specific license properties. The following table provides more information about this.
| Property | For a Grace License |
|---|---|
| Standalone/Network/Repository |
Network only To use grace licenses, your application must be linked with the integrated library for both network and standalone licensing. Only v 8.0 (or later) of the Sentinel RMS License Manager and client library support repository licenses. |
| Long or Short-numeric |
Long A grace enabled network license cannot be in short numeric license format. |
| Trial or normal license |
Normal A grace enabled network license cannot be used as a trial license. |
| License commuting | A grace enabled network license can be commuted. However, no grace period is available when a checked-out commuter token is being used on the local system. |
| License locking |
Grace licenses are installed on only those local systems that meet the local license request locking criteria. |
| Grace period duration |
As a developer, you can limit the length of the grace period by setting: >The maximum number of days—between 1 to 180—the application can be used for. >The total number of hours—between 1 to 1440—the application can be used for. NOTE The days counter will start when the application switches to a grace license and when this limit is reached, the grace license will expire regardless of remaining hours, if any. |
| Persistence based license |
Yes Grace license is a persistence data-dependent license model. You must set up the persistence data for allowing use of grace licenses on your customer's local computer, if using licensing libraries earlier than v8.4.0. In versions later than 8.4.0, grace persistence is set up when the LSRequest or its variant API is called. |
| Clock tamper detection enabled |
Yes A grace enabled network license can detect time tampering. To allow clock tampering detection, you need to initialize the computer at the time of installing the application. Execute sntl_persistence_create API. For more information on how to call, compile and execute this API, refer the sample available at …\9.8\Samples\C\Src\sntl_lspmgmtinit.c path. For more details, refer to Persistence Data-dependent license model . |
| Capacity licensing |
No A grace enabled network license cannot have capacity associated with it. |
| VM detection flag | A grace enabled network license can have VM detection check. However, this check is not applicable to grace license tokens when being used on local systems. |
| License revocation |
Yes A grace enabled network license can be revoked. |
| License sharing |
No License sharing rules are enforced by the License Manager to network licenses (which may also be used as grace license on the local system). A grace license token on a local system acts as a standalone license and therefore sharing rules do not apply to it. |
| License holding |
No License holding feature is useful for the network licenses. But when a grace license token is obtained on a local system, the license holding feature is not needed. |
| License Manager redundancy |
Yes A grace enabled network license can be used in the redundant License Manager setup. |
| Public vendor information | The public information is not included in grace license strings installed on the local systems. |
| Private vendor information |
Limited private vendor information (up to 465 bytes) can be included in grace license code strings. Prior to RMS v8.4.0, the grace code installation failed on the customer’s computer if you have specified lengthy values for properties like feature name, feature version, vendor information and secret text. Only private vendor information of approximately 64 bytes was supported in grace code. However, this limit has been increased in the 8.4.0 release. Now, the maximum length/bytes of vendor information that can be included in grace code is 465 (remaining bytes will be truncated). |
| License vendor information | Specify different software vendor data across participating licenses (maximum 512 characters). This field does not actually participate in license aggregation and is applicable to version 19 licenses and above. |
NOTE The grace license installation may fail on the customer’s computer if you have specified lengthy values for properties like feature name, feature version, vendor information, and secret text. In such cases, the VLSrequestExt2 API function will return VLS_GRACE_CODE_LENGTH_OVERFLOW_ERROR in the special_flag out parameter. However, this does not mean that these properties are incompatible with grace licenses. For example, the grace license is successfully installed if you specified up to 5 characters for the feature name and version each, no secret strings, or up to 55 characters (approx.) of private vendor information.