Known Issues

The known issues for the Sentinel EMS 6.1.100 release are categorized and listed below:

Related to Web Browsers

>A web page may appear unresponsive when handling huge data sets. To resolve this, increase the script timeout of the web browser.

>In Safari, the Copy Download link does not work.

Related to Features / License Models / Entitlements / Activations / Downloads / Webhooks

General

>If you experience issues with changing your password, it is recommended to use the Forgot Password feature to reset it.

>Only alphanumeric characters are supported in the file name for ESD.

>Support for ESD is not available for entitlements that include the special characters " or ' in the EID.

>Support for concurrent feature creation is only available with a unique feature identifier in the createFeature REST API.

>Support for concurrent product creation is only available with a unique product identifier in the createProduct REST API.

>Multi-byte characters are not supported in webhook names.

Sentinel LDK

When associating a feature with the Time from First Use license model, only Overwrite is supported in the Apply License field, even if Add is visibly selected.

For example, suppose that in Product 1, the license model for Feature 1 is configured to expire 30 days after the first use. The first time the user logs in to Product 1, the "timer" starts, and the expiration date is automatically set to 30 days from the current date. If, after 25 days, the user purchases Product 1 again for another 30 days, the expected result would be that the user would get a total of 35 remaining days (5 remaining days from the first purchase, plus 30 days for the second purchase). However, the actual result is that the user gets 30 days starting from day 25 because the previous license configuration is overwritten.

Sentinel RMS

>Features using the Flexible License Model and features using other Sentinel RMS license models cannot be added to the same product.

>Renewal and re-committal of lease-based licenses that implement dynamic substitution in their license is not supported.

>For leased licenses using default products, if the "Start from activation date" option is enabled in a license model for a feature, then the duration of consumption of a feature is overridden by the duration defined at line item level. For example, if, in an entitlement, the feature duration is for 1 year and the line item duration is for 2 years, then the feature can still be consumed for 2 years.
This issue is also applicable for leased variants in versionless products, regardless of whether the "Start from activation date" option is enabled or disabled.

NOTE
If the "Copy License Date from Line Item" attribute is enabled in the Administration Console, then the dates in the license model are copied from the dates of the line item.

>Sometimes, during an update of entitlements based on the Flexible License Model with Cloud LM (Cloud License Manager) as the deployment type, the license renewal process is not initiated due to back-end issues. In such cases, it is recommended to submit the renewal request again by updating the entitlement.

>When activating a connected entitlement based on the Cloud LM (Cloud License Manager) deployment mode, if the entitlement contains a line item to generate a future date exclusive license, then the activation state remains as "In Progress" because the license is not deployed.

>For a license model already associated with a feature of a product, using the create, update, or replace web services for products to associate a license model in the feature, where SAOT is set to "true" and the original license model is also specified, returns a successful response instead of generating an error. The product created, updated, or replaced through web service has SAOT set to "true" and the license model association is ignored.

>After creating a registration token, if the customer name and customer identifier are updated using the Sentinel EMS portal, then these changes are not displayed on the Registration Tokens page and the pages to edit or copy a registration token.

>Two activation records may be displayed under Activations when the lease is obtained for the first time on a device. This may occur even the entitlement was not updated and the lease renewal frequency was not reached.

>When adding a variant for a versionless product in the Sentinel EMS GUI while using the Flexible License Model, the “Apply Full Duration” and “Do Not Renew Automatically” checkboxes disappear. Instead, the corresponding numeric values—438000 and 2147483647, respectively—are shown in the “Lease Duration” and “Lease Renewal Frequency” text boxes. This does not affect the behavior of these fields.

Sentinel Fit

"Optional Features" are not supported for Sentinel Fit. Therefore, when working with products and entitlements, even though an option is provided that enables you to specify whether the feature can be included or excluded, you must retain the default "Included (Optional)" value. For more details, see the latest Sentinel Fit Developer Guide.

Related to Reports

>The date range for the report generation should not be greater than 1440 days.

>It is recommended using data export reports for data sets containing a large number of entitlements or activations (more than 20,000).

>Up to 24 hours may be required for the Electronic Software Delivery (ESD) data to be reflected in ESD reports.

>The Sentinel RMS usage tampering reports — “Customer Tamper Data" and "Customer Tamper List" — are not supported in Sentinel EMS 5.2 and later.

NOTE The details of these reports are retained in the Sentinel EMS User Guide as support information to maintain backward compatibility.