New Features and Enhancements
Release: 6.0
The following features and enhancements are included in the Sentinel EMS 6.0 release:
>User Management from Customer Portal
>Support for Sentinel and Vendor Identity Providers
>Support for One-Day Entitlements
> Data Export Usability Enhancements
>Allow Modification of the Entitlement as a Whole Attribute
>Friendly Name for Client ID in OAuth Client Management
>Enhancement in the Provisioning Payload
>Sentinel LDK Enforcement Version Updated to LDK 10.0
>User ID Field Restrictions for Customer's Users
User-Based Licensing
This release introduces user-based licensing that enables end users to access the software application by logging in with a user name and password. Unlike traditional machine-based licensing, where licenses are tied to specific machines, user-based licensing associates licenses directly with end users. This provides flexibility to end users to access their licenses from any machine—laptop, tablet, or mobile—using their login credentials.
User-based licensing is supported for Sentinel LDK from the vendor portal and customer portal.
For more details, see Sentinel EMS User Guide for Sentinel LDK.
Terminology Changes
In this release, the following terminology changes are implemented across all Sentinel EMS portals:
>Users are now Vendor Users
>Contacts are now Users
>Accounts are now Machine Accounts
Note that the REST API endpoints remain unchanged to maintain backward compatibility.
User Management from Customer Portal
Sentinel EMS now supports user management capabilities directly from the customer portal. This feature enables customer administrators to create and manage customer's end users from the customer portal.
For more details, see Guide to the Sentinel EMS Customer Portal.
Support for Sentinel and Vendor Identity Providers
Sentinel EMS now supports both Sentinel identity provider and vendor-specific identity providers for user authentication and management. Software vendors have the flexibility to use their own built-in identity provider for managing users. For vendors who do not have their own identity provider, Sentinel identity provider is provided as the default option.
For more details, see Sentinel EMS User Guide for All Enforcements.
Support for One-Day Entitlements
You can create one-day entitlements that start and end on the same day from the vendor portal and REST API. The start date and expiration date are same. This is especially useful when the ‘Copy License Date from Line Item’ Administrator Console property is set to Yes.
GUI Label Updates
In addition to the terminology changes, the vendor portal also has the following GUI label changes:
>Creation Date is now Revocation Initiation Date in the Revocation Attributes tab of the Activations page for better clarity.
>Product ID is now Product Identifier, Feature ID is now Feature Identifier, and Customer ID is now Customer Identifier to ensure that GUI labels depict the correct behavior.
>Executed By is now Operation Performed By in the Transactions page.
Search Dropdown Enhancement
In the Sentinel EMS portals, the Search filter is updated from a dropdown to a combo box. This usability enhancement enables users to either select a value from the available options or enter a search term directly as needed.
Data Export Usability Enhancements
In the vendor portal, you now easily navigate between the Data Export Reports and Data Export Downloads pages using the new options available under the Actions column of each page. This makes it easy to view previous data export reports, generate a failed report, or generate a specific report with different attributes.
Also, on the Data Export Downloads page, you can now expand a record to view the attributes used to generate the data export report.
For more details, see Sentinel EMS User Guide for All Enforcements.
Allow Modification of the Entitlement as a Whole Attribute
Sentinel EMS now supports modifying the Entitlement as a Whole attribute value from Yes to No when editing a completed or activated entitlement. This enhancement enables you to perform single line item activation.
This is a unidirectional support where modification is supported from Yes to No and not vice versa. Also, this enhancement is not supported for connected licenses.
For more details, see Sentinel EMS User Guide for All Enforcements.
Friendly Name for Client ID in OAuth Client Management
Sentinel EMS now supports specifying a user-friendly value for the Client ID when creating an OAuth client. If left blank, the Client ID is generated automatically.
For more details, see Sentinel EMS User Guide for All Enforcements.
Enhancement in the Provisioning Payload
Dynamic substitution in provisioning payloads can now include the customer object.
For more details, see Sentinel EMS User Guide for All Enforcements.
Sentinel LDK Enforcement Version Updated to LDK 10.0
Sentinel EMS portals and the REST API have been updated for the latest Sentinel LDK version, 10.0.
User ID Field Restrictions for Customer's Users
When creating a customer's user, only the underscore character is now supported as a special character in the User ID field. Other special characters, including those commonly used in email addresses, are not allowed. To maintain backward compatibility, if you are using the Sentinel EMS REST API and the User ID field is left blank, the user's email address is automatically copied into the User ID field.
Note: This applies only to customer's users (previously, contacts) and not to vendor users and channel partner users.
Miscellaneous Enhancements
>For a download that is not associated with any customer, the GET download API now returns details of the given download irrespective of the customerId given in the request. Earlier, the API endpoint did not return any records if the customerId was provided in the request for a download which was not associated with any customer. For more details, see Sentinel EMS REST API Reference.
>When no downloads are included in the entitlement or license certificate, the Downloads section in the email body is not displayed.
>Sentinel EMS now enables you to update associated products for completed product suites that have not yet been deployed. Note that product suites are supported for Sentinel RMS and third-party enforcements. For more details, see Sentinel EMS User Guide for All Enforcements.
>Sentinel EMS now supports pagination to handle a large set of channel partner users for an associated channel partner.
>Usage reports are removed from the Reports page because these reports are already available from the Data Export Reports page. For more details, see Sentinel EMS User Guide for All Enforcements.
>The response of the GET Entitlement and Search Entitlements endpoints are corrected to remove totalRegisteredQuantity that was incorrectly displayed inside the productKeys object. This information is available with the entitlementFingerprints object. Also, in the Manage Fingerprints page of the vendor portal, the values of available quantity, activated quantity, and registered quantity are now correctly displayed when a product is not selected.