Resolved Issues

The Activations page displayed fingerprint values in lowercase under the Activation Attributes tab instead of preserving the original case.

Sentinel EMS did not complete activation for custom or third-party license generators when an external ID was specified at the activation level.

For Sentinel LDK activations, uploading a C2V file on the Activations page failed when the file extension was in uppercase.

The Activate button on the Entitlements page remained disabled when a user selected an entitlement after expanding it in the search results, requiring a page refresh to enable the button.

When splitting a Sentinel LDK entitlement containing versionless products, Sentinel EMS returned an internal error if a user email address was not provided in the sendNotification parameter.

Updating an entitlement did not correctly update the last modified date or transaction timestamps, resulting in incorrect results when searching for modified entitlements.

In an entitlement where a product’s feature has multiple license models, changing the license model did not correctly update the locking criteria.

Adding a new line item to a cloud-connected entitlement using the Replace Entitlement API resulted in an error when Entitlement as a Whole was enabled.

Disabled license models appeared in the license model dropdown when configuring a product feature.

Vendor users with all customer management permissions were not allowed to manage user associations from the vendor portal.

When creating a user association using a fully copied Key ID in the vendor portal, the key was not loaded or could not be selected, while partial Key ID input worked as expected.

User association with a Sentinel Key failed when the key description contained parentheses.

A vendor user could not activate an entitlement due to insufficient role permissions within the assigned market group.

Sentinel EMS allowed creating a user for a customer in a different market group through the REST API, resulting in the customer and user belonging to different market groups.

Standard vendor users could not generate the Customer Entitlement report because the mandatory Customer Ref ID field was not visible to them.

Generating the Products report on the Generate Data Export page failed with an error because the report ID was used instead of the report name in the report generation request.

In the customer portal, only the first 10 downloads were visible when a product had more than 10 associated downloads, and navigating to later pages caused the pagination controls to disappear.

Sentinel EMS did not accept Webhook endpoint URLs containing special characters such as _ and == when used as part of an access key in the URL.

The keyId parameter was missing from the response of the Add Activation API.

The Search Activations API incorrectly returned Sentinel RMS as the enforcement type for a Services activation when a versionless product contained both Sentinel RMS and Services variants, and the Sentinel RMS variant was activated first.

The Entitlement API endpoints allowed duplicate features in a line item during POST and PUT operations instead of ignoring duplicates and including only a single feature.

Updating a customer using the PATCH API returned an internal error when modifying the customer identifier for deployed entitlements using the Flexible license model with on-premises network deployment mode.

The Delete Fingerprint API endpoint intermittently returned a 503 error and showed degraded performance when processing fingerprints associated with a large number of line items.

The Search Machine Accounts API returned an empty response for standard users when they did not have access to any machine accounts, while Administrator and Service Account users received the expected results.

The Add Product API returned an error when the isLDKEnforcement field was included in the request payload for enforcements other than Sentinel LDK.

The CSV feature import processed only the first license model for features with multiple license models, resulting in incomplete feature creation, while JSON import worked as expected.

The CSV product import included only the first memory record for products with multiple memory files, while JSON import worked as expected.

During migration from Sentinel LDK-EMS to Sentinel EMS, memory data was missing for some entitlements.

The migration incorrectly associated admin users with market groups, which restricted editing of the migrated market groups.