On the “Licensing Options” tab, you can define required licensing logic for your application by choosing licensing data objects of predefined types, such as Expiration Date, Run Counter, etc.To edit the value of a data object press related “Change” button
For the most DataObjects you have the choice between “CDO” (Crypted DataObject) and standard DataObjects (“CDO” deactivated). CDO offers additional protection against manipulations, so we recommend to keep this option activated. If you plan to combine AutoCrypt and API implementation and additionally want to query these Crypted DataObjects via API commands, please check the sample code in our PPK and corresponding readme files for CDO compatibility. Not all API libraries offer CDO support, eg. for older or exotic compilers. Please contact our Technical Support for any questions. |
To remove the data object, click the check box or radio button near data object and confirm the message that you want to delete it with "Yes".
The following types of licensing data objects are supported:
Network License | network license counter value of the application |
Run Counter | number of application executions (runs) |
Expiration Date & Time | exact date and time when the protected application is going to expire, for example "31 DEC 2016 23:59:59"; |
Expiration Date | fixed expiration date, submitted in the format “31 DEC 2016” - this data object type is obsolete and only preserved for compatibility purposes, please use “Expiration Date & Time” instead |
Relative Expiration Date | The “Relative Expiration Date” specifies the number of days the application is allowed to be used from the first run. i.e. counter is activated on the first application launch |
Expiration Days | “Expiration Days” is a flexible expiration date, submitted as number of days the application is allowed to be used, starting from the day the CRYPTO-BOX was formatted. |
Expiration Time | real-time expiration, submitted as period of allowed application usage (in seconds); |