When generating Activation Codes programmatically using the COM-Activator, you can easily override an Authorization Request to generate an Activation Code which corresponds to a completely different Authorization Definition.

Although it will not be necessary often to override an Authorization Request, it gives you the option when inspecting Authorization Request Codes, using the COM-Activator, to make the decision to provide the customer with an Activation Code that may do something completely different than what was requested.

Example

You might have numerous features in your software which are individually available for purchase, you have chosen to use an Authorization Definition for each one (or set of features). A customer uses your software to get the Authorization Request Code for feature #1 (for example), but accidentally clicks the wrong button and gets the request code for #2.

Unknowingly, he purchases feature #1 from your site. When you decode the Authorization Request Code programmatically with the COM-Activator you see immediately that he made a mistake. You can see clearly that the request corresponds to a feature he did not pay for (#2). Instead of calling the customer and asking him to repeat the process so you can get the correct Authorization Request Code, you simply override the request and issue an Activation Code for feature #1. The customer doesn't even need to know he made a mistake.

Note that although you may override an Authorization Request Code, you must still have one to begin with - or generate an Activation Code directly from a FingerPrint.

More Information

For more information on using the COM-Activator, see: SoftwareShield COM Activator Component