Trigger Code Activation

A Trigger Code is a one-time encrypted numeric message that is sent to your application to perform any action. Once your application is installed, your client will need to activate the application, and each activation will have a Trigger Code. You can use Trigger Codes to remotely access or activate special functions that your client does not know exist. Trigger Codes are randomized with a user-supplied seed that prevents other Instant Protection PLUS 3 users from unlocking your application. The full list of Instant Protection PLUS 3 trigger codes can be found here.

Trigger Code Event Data

In some cases, sending numeric data along with the Trigger Code is extremely useful. Trigger Code Event Data may be used to send the number of days a periodic license will execute, extend the days a trial will run, or send any value that your application could use by utilizing the Instant Protection PLUS 3 API.

Trigger Code Event Data can also be used to send module information such as which module bits should be enabled. This prevents the need of sending multiple Trigger Codes in order to turn on multiple modules.

Trigger Code Summary

A summary of the different pieces of information used during activation is below. This will help you establish a more complete understanding of how activations work.

Important

When using activation with SOLO Server, the Trigger Code Seed and RegKey2 Seed values in your application's source code must match in all relevant product options configured in SOLO Server (which may be used to create License IDs used to activate your application over the Internet).

Trigger Code Seed: This is the "seed" value used when generating Activation Code 1. Typically, this value should be unique between each of your products/applications so that you may prevent them from being cross-activated. (In other words, using a unique Trigger Code Seed value for each product prevents activation codes generated for "Product A" from being used to activate "Product B"). The value specified must be a number between 1 and 65535. When allowing activation through SOLO Server, your application's source code and the corresponding product option(s) in SOLO Server must have matching values.
RegKey2 Seed: This is the "seed" value used when generating Activation Code 2. Typically, this value is also unique between each of your products/applications so that you may prevent them from being cross-activated. The value specified must be a number between 1 and 255. When allowing activation through SOLO Server, your application's source code and the corresponding product option(s) in SOLO Server must have matching values.
Trigger Code Number: A Trigger Code Number is simply a number between 1 and 50, which defines the action(s) which will be taken when Activation Code 1 is successfully validated on your customer's computer. When a customer requests activation, you or your company is responsible for selecting the appropriate Trigger Code number when generating the activation code(s). (When using SOLO Server, this is configured on the product option selected when the license was created or purchased.) As the application developer, you are free to assign and program your own set of actions for any given Trigger Code Number. So for example, you could program your application to activate a non-expiring (or perpetual) license for your application when it receives a Trigger Code number of 1. At the same time, your application could also be programmed to activate a time-limited (or a "lease" or "periodic") license for some arbitrary number of days when it receives a Trigger Code number of 10.
User Code 1: Also known as the "session code" to former Protection PLUS 4 SDK users, this value is a randomized value that makes activation codes unique to each activation attempt. Its purpose is to prevent end-users from using an activation code more than once, which is very important when an activation code does something such as incrementing a counter value. When users contact your company to activate, they will be required to provide this value.
User Code 2: Also known as the "Computer ID" to former Protection PLUS 4 SDK users, this value is generated from device-specific information. Its purpose is to make each activation code unique to the PC for which it was issued, and prevent users from activating "Computer B" with an activation code generated for "Computer A". When a users contact your company to activate, they will be required to provide this value.
Activation Code 1: When a user requests activation, this value is generated by you or your company. This value must always be provided to your end-users to complete an activation. Once your protected application has successfully validated Activation Code 1, it receives the Trigger Code Number, which allows your protected application to alter its license file as appropriate.
Activation Code 2: When a user requests activation, this value may (optionally) be generated by you or your company in order to send a secondary, numeric value to your application during activation. The decoded value sent to your application through Activation Code 2 may only be up to 14 bits in length (possible values range from 0 to 16383). For example, when issuing activations for a time-limited (or a "lease" or "periodic") license, this value can include the number of days which the protected application is allowed to run.