Automated License Validation

In addition to validating the local license file every run, a licensed application can also periodically validate with SOLO Server Automation. Attempted validations can fail silently, but required validations must be successful otherwise it will disable use of the application. This stops a user from blocking connection to SOLO Server Automation to avoid the validation.

You should only need to validate with SOLO Server Automation periodically, as validating too often can result in adverse responsiveness, especially if your customers do not always have a stable Internet connection.

Day-based periodic validation: When this feature is checked, the application will attempt to communicate with SOLO Server Automation in order to validate the license. The frequency of these online validations may be customized as well by the number of days between each validation. This feature allows changing the status of a license remotely through the SOLO Server Automation interface which will update the status of the local license when the next validation occurs.

Attempt validation with server every x days(s): Sets the validation with SOLO Server Automation frequency in days . If the application is unable to communicate with SOLO Server Automation, no error occurs.
Require validation every x day(s): When checked, this feature sets the validation with SOLO Server Automation frequency in days . If the application is unable to communicate with SOLO Server Automation after the validation frequency day has passed, the application will not execute until it can communicate. You must use a require validation option to securely enforce remote deactivations.
Warn user x day(s) before lockout: A customizable warning message will display if the application is within x days of the Require validation day. Only used when Require validation is checked.

Runs-based periodic validation: When this feature is checked, the application will attempt to communicate with SOLO Server Automation in order to validate the license. The frequency of these online validations may be customized as well by the amount of times the application is run. This feature allows changing the status of a license remotely through the SOLO Server Automation interface which will update the status of the local license when the next validation occurs.

Attempt validation with server every x run(s): Sets the validation with SOLO Server Automation frequency in the amount of times the application is run. If the application is unable to communicate with SOLO Server Automation, no error occurs.
Require validation every x run(s): When checked, this feature sets the validation with SOLO Server Automation frequency in the amount of times the application is run. If the application is unable to communicate with SOLO Server Automation after the validation frequency runs has passed, the application will not execute until it can communicate. You must use a require validation option to securely enforce remote deactivations.
Warn user x run(s) before lockout: A customizable warning message will display if the application is within x runs of the Require validation runs. Only used when Require validation is checked.
Validation Warning Message: A customizable warning message displayed when using one or both of the Warn user before lockout settings. Using the variable [varPeriodicLeft] in the text will have it replaced with the actual number of runs/days left until validation is required.

Validation Failure Message: A customizable message displayed when using the Require validation setting and the application is beyond the allowed number of days and/or runs and has not communicated with SOLO Server Automation. Only used when Require validation is checked.

License Revoked Message: A customizable message displayed when a validation with SOLO Server Automation has reported the license as being invalid.

Next Step