My advice is that you generate your own licenses on the fly (ie. technique #2). My generator uses personal info from the user (ie. their name or email address) to create the key, therefore #1 is out (which seems very unsecure anyway). As for #3, I never looked into Plimus' generator, but I have 2 concerns about it: a) If someone hacks Plimus' generator, does that mean any software used by their generator can be cracked? and b) It locks you into someone else's system.

Hi Malcolm,

1. With this licensing option, you need to upload pre-generated license keys to a licencse group. Each time a transaction is made, a license key(s) is deducted from your license group.

2. The way the Custom HTTP Request works is:

Once the order is processed we call the URL to generate the key with available parameters and use its OUTPUT as the key(s).

For example:

We have your script written in asp called keyGen.asp that resides on our servers, the script takes the email address of the customer and returns a key in the format of DDD - XXX. after the order was placed we call that script with the email address as the input:

http://www.our_servers.com/keyGen.asp?yourVariableName=

What ever is returned from your script will be placed in the email sent to the customer in place of the tag which in this case would be the value of DDD - XXX.

Your script would look like the following:
----------------------------------------
Sub subName( yourVariableName )
{
your algorithm to make a unique id.
..
Response.Write(DDD - XXX)
}
----------------------------------------

3. The format of the key is:

The license key is generated when the order is submitted/processed. In the instructions of this licensing method (found in the "license keys" section of a contract-id), you can set the usage count, which insures that the license can not be used on multiple machines.

If you have any further support queries, please contact our Vendor Support Team at vendors@plimus.com at anytime.