License Server Cloud-Ready has been enhanced with a new feature that allows temporary borrowing of HALCON licenses starting with version 25.11.
This capability is useful in situations where network access may be unavailable—for example during travel, remote maintenance, or to ensure that a network outage does not interrupt production.
Borrowing can be performed either through a simple user interface or via a JRPC API request, offering maximum flexibility for different workflows.
You can borrow a license up to 6 weeks in advance for a maximum duration of 7 days.
During the borrowing period, the license is reserved exclusively and cannot be used by others.
The borrowed license is provided as a license.dat file, which can be deployed in the usual way.
CodeMeter Package has been updated to 8.40b.
In rare cases the License Server could crash sporadically.
This problem has been fixed.
The Linux version of the License Server generated a .system instead of a .service systemd service file.
This problem has been fixed.
The documentation has been extended and made available online.
Added support to run the License Server as a native system service on Windows and Linux (via Windows Service Manager and systemd), and introduced logging to file with log file rotation.
Licenses without an expiration date were incorrectly interpreted as older than expired licenses during an update, causing expired licenses to be treated as updates.
This problem has been fixed.
In rare cases, when updating a license served by the License Server, the “licenses in use” metric was computed incorrectly.
This problem has been fixed.
Added support for the new edition model of HALCON 24.11. Starting with HALCON 24.11 a HALCON Progress license also unlocks the HALCON Steady edition.
If a request for a HALCON Steady license >= 24.11 is received, the License Server checks first if a valid HALCON Steady license is available, and then falls back to use a valid HALCON Progress license if available.
We have simplified the licensing process by removing the requirement for license slots.
Now, both License Server Cloud-Ready and License Server On-Premises variants also accept licenses which are not bound to slots.
License Servers that served different licenses (regarding version and modules) did not select the ideal license when a new request for a license was made.
This problem has been fixed.
Revalidating a session with an expired license resulted in a deadlock in the session handling.
This problem has been fixed.
Renew the License Server certificate to enhance its longevity.
It no longer comes with an expiration date, ensuring uninterrupted service.
Update handling of disconnected dongle.
The license server does not shut down anymore when the dongle is disconnected.
Instead, license issuance is paused until a valid dongle is reconnected.
This provides a more resilient and uninterrupted service experience.
Add a new health endpoint showing the protection state of the License Server.
Add client remote address as part of session metrics as optional configuration.
By default, it is deactivated.
Add licenses dynamically without restarting the License Server.
Improve handling of update licenses.
When two licenses with the same UUID but different expiration dates are found, the license server will only keep the one the expires later.