Revision History
This section describes enhancements implemented and issues resolved in the last three major releases of Sentinel Run-time Environment.
The revision history for earlier versions of Sentinel Run-time Environment is available at: https://docs.sentinel.thalesgroup.com/ldk/LDKdocs/RTE_History/Default.htm
Enhancements in Version 8.52
No enhancements are included in this release.
Issues Resolved in Version 8.52
Reference | Description |
---|---|
SM-132184 | When calling the applyV2C function of the Cloud Portal service, the MEM usage of the License Manager container continuously increased, forcing the License Manager to restart. |
SM-132507 | When using the GCP load balancer, it uses multiple instances to dispatch a runtime API request to the LMS. As a result, the LMS regards the request as coming from different machines, and more seats were incorrectly consumed. |
SM-132542 | Product names were not stored in the database, but were stored in lic_name.dat. As a result, Sentinel LDK Cloud Portal did not show correct product names after Docker instance was restarted. |
SM-132825 | On the Sessions page in Sentinel Admin Control Center, Key information was incorrect and Location information was missing. |
Enhancements in Version 8.51
Reference | Description |
---|---|
SM-98674 |
Sentinel License Manager now supports client identity registration on a user's machine when the user click a provided link. The License Manager Service can parse and decode the URL to copy the identity string to the local INI file. |
SM-128094 | Sentinel Admin API can now be used to obtain a C2V file or fingerprint file from a user's machine. |
Issues Resolved in Version 8.51
Reference | Description |
---|---|
SM-121764 |
Detection of Amazon EC2 has been improved. |
SM-122150 | The License Manager would fail on machines with a CPU from before 2010. |
SM-123325 |
The recipient list of detaches was incomplete when working with secure storage. (The list is complete when working with trusted storage.) Note: This issue did not affect functionality - it only affected the user interface. |
SM-124009 SM-130468 |
The PMType2 clone detection scheme did not work correctly under certain unusual circumstances. |
SM-126115 |
The Admin License Manager would always checks the idle timeout, while the Runtimeless API never checks it. As a result, when installing or uninstall the RTE, conflicting behavior might occur for an HL Driverless key. Now, if the logged-in Feature on the key is not enabled for network access, idle timeout is skipped. |
SM-127056 | The listing in Admin Control Center of products with detachable features did not paginate correctly. |
SM-128810 |
For Sentinel Licensing API, when a call to hasp_login_scope() fails, the event is now logged with the related feature_id, as was already occuring with hasp_login(). Until now, the behavior for the two functions was inconsistent. |
SM-130889 |
The License Manager Service was not able to access a cloud license manager hosted by Google Cloud Platform with proxy settings. |
SM-131117 | In Admin Control Center, automatic detach was not taking friendly names for Feature and Product names. |
Enhancements in Version 8.43
No enhancements are included in this release.
Issues Resolved in Version 8.43
Reference | Description |
---|---|
SM-120179 |
The zlib library has been upgraded to version 1.2.12. |
SM-121566 |
During installation of Run-time Environment 8.41 on a machine with an old CPU, installation would fail with a message similar to: Error when starting the Sentinel License Manager service with parameters 1280 0 0.
|
SM-121764 | The Sentinel License Manager for Intel did not use both interfaces (legacy and next-generation) to read the HDD_UID. The use of both interfaces is preferred to avoid duplicates. |
SM-123325 |
In Admin Control Center, the displayed recipient list of detached licenses was incomplete when the Sentinel License Manager worked with Secure Storage. This issue would not occur when working with Trusted Storage. This issue did not affect functionality of the License Manager. |
Enhancements in Version 8.41
Reference | Description |
---|---|
SM-97094 |
You can now set an expiration date for client identities. This enables vendors to: >Easily manage trial by providing users with expiring identities that consume the same license. This removes the need to generate a new key and a new license for each trial. >Manage which users can access a concurrency license and for how long. |
SM-109039 |
High Availability for cloud licensing now supports configuration of active-active license servers To support this functionality, VLIB 8.41 or later must be deployed on the license servers. |
SM-111379 |
The License Manager now supports the use of dynamic memory for SL AdminMode keys . To support this functionality, VLIB 8.41 or later must be deployed with the Run-time Environment. |
Issues Resolved in Version 8.41
Reference | Description |
---|---|
SM-119586 |
After connecting to a VPN, when you click Submit on the Access to Remote ACC panel, a false-positive warning similar to the following was sometimes displayed: "A duplicate License Manager ID exists on this server and on the server at address 10.42.49.253. This is typically caused by cloning a VM. Licenses on these two servers may be inaccessible" |
SM-119327 |
If no host is specified, AdminAPI uses "localhost" to connect to the License Manager. But in modern machines, localhost is resolved to "::1". This may not work because the IPv6 option may be disabled in the License Manager. AdminAPI now uses "127.0.0.1" instead of "::1". |
SM-115393 |
When the client identity is installed in Admin Control Center, and the License Manger received a detached license from a remote machine, a local API was affected by the local License Manager detachable configuration. However, the local License Manager should have only acted as the forwarder in this case. |
Enhancements in Version 8.31
Reference | Description |
---|---|
The License Manager now supports storing licenses in a trusted license storage on the software vendor's server. As a result, License Managers can now be configured to support high availability for cloud licenses. | |
SM-108300 |
Admin Control Center help system now describes how to set a user name for the ACC administrator. Setting a user name helps to improve security for Admin Control Center. For details, open the Admin Control Center help. From the list of links at the bottom of the pages, click Configuration > Managing User Access to Admin License Manager Information > Setting a User Name for the ACC Administrator. |
Issues Resolved in Version 8.31
No issue are resolved in this release.
Enhancements in Version 8.23
Reference | Description |
---|---|
SM-17686 |
A customer can now detach one or more seats with concurrency from a cloud license server and install them on a machine with a client identity. Applications on remote machines in the same LAN can then consume seats from this machine. This enables customers to: > Set up second-level license servers. > Control the number of local hardware resources used by an application. |
SM-99835 | The Admin License Manager now supports Internet Protocol version 6 (IPv6). |
Issues Resolved in Version 8.23
Reference | Description |
---|---|
SM-98723 | The License Manager would log each individual Feature request from other License Managers. This resulted in an excessive number of entries in the License Manager log file. |
SM-99308 |
When connecting with port 80, Login/Logout/Encrypt API calls to cloud SL keys installed on a cloud license server would cause repeated WSAECONNREFUSED and ESELECTTIMEDOUT errors on the client machine. |
Enhancements in Version 8.21
Reference | Description |
---|---|
Admin Control Center has been updated to keep it consistent with changes in the appearance of Sentinel LDK user interfaces and documents to match other Thales products. | |
SM-89762 | The Run-time Environment now supports protected applications executing in LXC Linux containers. |
Issues Resolved in Version 8.21
Reference | Description |
---|---|
SM-91083 | A user of Admin Control Center was not able to clear the password for accessing or configuring the License Manager once a password has been set. |
SM-93806 | Sentinel Admin API would return invalid XML when the Issue To field of client identities contains some special characters. |
SM-93811 | When a user would attempt to rehost a license from RTE 8.1x to an RTE version lower than 8.11, the error 30 HASP_INV_SIG was returned. |
SM-94573 |
With cloud licensing, when opening a remote session, the session would be closed after 15 minutes if no hasp call was made on the session. This resolution fixes the keep-alive timeout. |
SM-96073 | The License Manager would fail under certain circumstance when working with client identities. |
SM-96715 | Memory leak while using identity sessions have been resolved. |
SM-97123 | Firewall compatibility for identity communications has been improved. |