v2.12-rc3: Fix signature verification failed error

In this update, we have changed which RSA Public Key is used to verify the configuration string. Previously, we would either use the Cryptolens RSA Public Key or your account specific RSA Public Key, however, since this release, in all instances the Cryptolens RSA Public Key will be used.

This also means that you would need to generate a new configuration string from the following page: https://app.cryptolens.io/extensions/LicenseServer.

Updates
2023-12-14: Added compiled binaries.

v2.12-rc2: Read configuration string from environment variables

This release adds the option to load configuration string from the environment variables. You can read more about it on this page: https://github.com/Cryptolens/license-server#alternative-ways-to-configure-the-server.

This means that all features of the license server are supported by only using the binaries. There no longer a need to compile the license server if you would like to use the local floating license server.

Note: you need to re-create the configuration string again on this page, in case you generated one for previous versions of the license server.

v2.12-rc: Add support for environment variables and pre-compiled binaries

This update comes with two major changes:

1. It allows you to use environment variables to change parameters (such as port and path to activation file folder), which can be useful if you plan to run the license server as a service and do not want to compile a new version of the server for each client.
2. We provide pre-compiled binaries with default values, that can be overridden with a configuration file or environment variables.

v2.11: Custom port, clarified error messages and minor fixes

This update introduces several bug fixes, clarification of error messages and ability to override the port using a config file, when a Configuration String (generated with https://app.cryptolens.io/extensions/licenseserver) is used.

v2.10: Updates to Deactivation offline

In this update, an issue was fixed when Key.Deactivate would not return a response in the local floating license server.

v2.9: Implement deactivation offline and clear old machines (floating)

This update introduces the following changes:

1. Deactivate now supports the local offline license server, when Floating=True in the Deactivate call. In other words, it allows you to release machines earlier than then the specified FloatingTimeInterval.
2. Add a process that clears old floating license machines in offline mode.

v2.8: Hide machines that have expired (floating offline)

This update fixes an issue where the GetKey method (when being used with floating licensing offline) returned devices that have already expired. This issue did not affect Key.Activate, i.e. machines could still not achieve the limit, even if GetKey returned the old devices.

v2.7: Update apiUrl and pass on API errors to client SDK

This update comes with the following changes:

1. All requests are now forwarded to the new API endpoint, i.e. api.cryptolens.io.
2. The content type that is returned is now the same as the one from the API, i.e. application/json.
3. In case of an error (400 or 500) from the API, it will be passed on to the client library.

v2.6: Record local IP and Friendly name (floating licenses offline)

Fix an issue with GetKey not recording IP and Friendly Name

v2.5: Support GetKey and bug fixes

• Add support for GetKey (note, when local floating server is enabled, the RSAPublicKey that was generated using this page needs to be used.)
• Bug fixes.
• Clarify how to create a configuration when the license server is running as a Windows service.