Use cases

You want to protect your application by using license files. This is done by linking in LM to your software and verifying license files. Using License Manager you can quite easily develop a software and link in the LM static library which you built using keys generated by the license key generator. Below you see a schematic of how things are set up. Lets say that you named the project A in the build script.

1. When building license manager the build script will check if the Project A project structure with secret and public keys are in place. Otherwise it will run the license key generator to initialize this folder structure. Note, you should keep the Project A files safe for the lifetime of the software.

2. After building the license manager you will get a static library to link into your own software.

3. Install software on target (V700/V1000/V1200)

4. Generate license file using the License key generator and put it on target.

5. From your own software, check if the license file is valid by calling functions in LM.

• The license file cannot be tampered with since it is signed with the secret key stored in a safe place (that is your responsibility).

You can also bind a license to a specific target device by first prompting it for its hardware ID using the lccinspector tool or by making it visible in the UI of your software. Using the license key generator you can add the hardware ID as a parameter to make the license unique to one device. More on that workflow under the workflows chapter.