Linking the execution of a software to a. With the recent coming of virtualized environments the installation of software directly on the machine has been less and less.
OpenLicenseManager guess the environment where the user is trying to launch the software, and reports it to the software publisher when he is generating a license in a way that he can decide how to limit the usage on per license basis.
This is straightforward case. If the software is executing on a physical hardware it is possible to identify the hardware by various parameters (cpu type/memory/disk label/mac address)
Generating a hardware identifier on a virtual machine doesn't make much sense, since the vm can be copied as a whole elsewhere
and there are few ways to detect this without using an external license server.
Depending on how containers are used having hardware identifiers may make sense or no sense at all. For instance if containers are used
to avoid to pollute the external distribution it makes perfect sense to have an hardware identifier, if users are running dockers in a kubernetes cluster it makes no sense at all.
Below the identifier generation workflow.
If the licensed software specify the parameter
If the licensed software uses STRATEGY_DEFAULT
and the strategy generates an unstable identifier it is possible to ask the user to set t