The Accounts page allows you to create the activation (or user)
accounts for licensing your software products to the user.
To add an account, use the Insert New Account button. Each new
account is given a unique Activation Key and User ID in which both are randomly
generated. You can then edit the newly added account to select the licensed
product and enter the user information. To license the product, you can simply
send the Activation Key to user. The user can then use the Activation Key to
activate the application instantly online, through the Activation Server.
You can also add new accounts in bulk by entering the number in the New
Account edit box, select a product from the list, and click the Insert
New Account button. By default, the maximum number of accounts for bulk
addition is 10. You can change it in the Web.Config
file, under the key MaxAccountAdded. Below is an
example.
<add key="MaxAccountAdded" value="10"/> |
The Search box allows you to search the activation accounts.
Enter your search term and click the Search button. It will find a match
in the following fields: UserID, ActivationKey,
RegName, RegOrg, Seller, PurchaseID, FirstName, LastName, Company, Email, Street, City, State, Country, and
LoginUser.
You can search by product from the Search by product drop-down
list. Click the Filters button, you can filter
your search results by status of Activated, Destroyed, and Disabled.
To export the activation accounts as a CSV (Comma Separated Values)
file, use the Export button. From the Export drop-down list,
select Activation Key to export the Activation Keys only; or, select User
Information to export the activation accounts including the Activation Key
and user information.
NOTE: When you make an export, a temporary exported file is created in the
Exported\ folder of the Activation Server. The file name is AK<random
number>.CSV or UI<random number>.CSV, for the exported Activation
Keys or user information, respectively. For instance, https://demo.eleckey.net/exported/AK12653984.csv https://demo.eleckey.net/exported/UI645887084.csv To ensure the security, after you save
the exported file, it is recommended that you remove them from your
Activation Server. |
The fields in the Accounts table can be grouped into the following
categories.
The following fields are used for licensing the products, as well as
managing the activation accounts.
Select the licensed product from the list that links to the Products
table.
The UserID is randomly generated. However,
you can edit it as you want. The UserID is encoded
into the License Key when the Activation Server generates it to respond to the
license activation request. When activated, the UserID
will be saved in the Key of the protected application, which can be used as the
user identification.
The Activation Key is randomly generated. The default format is a
20-digit hexadecimal number (e.g. 3CB9-EE94-FA7B-49F4-5D62). However, you can
edit it or change the format as you want.
The Activated checkbox shows the status of activation. It is
automatically checked when the user activates the license, and unchecked when
the user deactivates the license.
The Destroyed checkbox shows the status of license destruction. It is
automatically checked when the user destroys the license, and the Activation
Server has received and verified the Destroy-Code.
In addition, the Destroyed checkbox allows you to command the protected
application to destroy its license. This feature is useful for fight against
fraud or stole accounts. In order to use this feature, you must enable automatic license update in the protected
application. As a result, the application regularly connects to the Activation
Server to validate the license. When you enable this checkbox, the next time
the application connects to the Activation Server; it will automatically
destroy its license.
The Disabled checkbox allows you to disable the activation account. As
a result, the user can no longer use the Activation Key to activate the
license.
The registration name field is used with the application protected as
shareware. In this case, the protected application requires the user to enter
their name and organization in order to activate the license. This field is
filled automatically when the user activates the license.
The registration organization field is used with the application
protected as shareware. In this case, the protected application requires the
user to enter their name and organization in order to activate the license.
This field is filled automatically when the user activates the license.
The following fields (Seller, PurchaseID,
PurchaseDate) contain information about sales
and ecommerce. You can enter sales information in these fields. If you have set
up the Activation Server to interface with an ecommerce provider such as
Share-it! or PayPal, these fields are filled automatically.
The following fields (FirstName, LastName, Company, Email, Phone,
Fax, Street, City, Zip, State, and Country)
contain information about the user. You can enter the user information in these
fields. If you have set up the Activation Server to interface with an ecommerce
provider such as Share-it! or PayPal, these field are filled automatically.
The fields LoginUser and LoginPassword are optional, in case you want to set
up a web page that allows the user to access their account.
The following fields are used for license replacement. The Activation
Server will respond to the license activation request if the ActivationCount has not reached the MaxActivation.
The MaxActivation field comes from the
properties of the licensed product in the Products table. It specifies the
maximum number of activations allowed. The MaxActivation
of -1 means unlimited activations.
The ActivationCount field counts the number
of activations. It is incremented by one each time the user activates the
license, until it is equal to the MaxActivation. It
is decremented when the user deactivates or transfers the license back to the
Activation Server. If the MaxActivation is set to -1
(or unlimited activations), the Activation Count is not used.
The ActivationPolicy field comes from the
properties of the licensed product in the Products table. You can edit it to
enable or disable the policy.
The MasterIDCust and MasterLicenseCust
fields are used for license customization or upgrade, which allows you to
customize the license for each individual activation account. When both fields
are available, the Activation Server uses them to generate the License Key,
instead of the MasterID and MasterLicense
of the licensed product in the Products table.
When you apply an upgrade from the Upgrades table to the activation
account, the Activation Server merges the account’s current license and the
upgrade license, and generates a new pair of Master ID and Master License to
the MasterIDCust and MasterLicenseCust
fields automatically.
It is also possible that may create a different licensed product for
each individual account. In this case, you need to create a base product in the
Products table that specifies the properties e.g. ProgramID,
MaxActivation, ActivationPolicy,
but without MasterID and MasterLicense.
Next, associate the account with the base product. Finally, use LicenseKey Manager to generate the Master ID and Master
License for your customized product, and save them to the MasterIDCust
and MasterLicenseCust fields.
Specify a Master ID for license customization.
Specify a Master License for license customization.
The Reactivation checkbox is enabled automatically when a product
upgrade is applied to the account. For the upgrade to take effect, the user
must reactivate the protected application either by manual activation or automatic license update (if enabled). In
response to the license reactivation request, the Activation Server uses the MasterLicenseCust (if available) or MasterLicense
respectively, to generate and return the License Key. Note that, during
reactivation, the ActivationCount is unaffected. The
Reactivation checkbox is cleared automatically after the reactivation is
completed.
The LicUpgradeID field provides additional
upgrade information, which is automatically incremented by one when a license
upgrade is applied to the account. The field is useful to support license
activation from multiple machines either by manual activation or automatic license update (if enabled).
During the license activation request, the protected application compares the LicUpgradeID sent from the Activation Server against the
one in the Key. If the LicUpgradeID on the server is
different, the protected application reactivates the license through the
Activation Server, and then updates the LicUpgradeID
to the Key. Note that, during reactivation, the ActivationCount
is unaffected.
The following fields are used for license deactivation (or license
transfer to the Activation Server). When the user deactivates the license, it
is removed from the machine, and transferred back to the Activation Server.
License deactivation works as follows. The protected application first
requests the RegIDTran from the Activation Server.
Then, it encodes the current state of the Key Properties with the received RegIDTran, and generates the License Key (or called LicKeyTran) to be returned to the Activation Server, via the
license deactivation request.
The RegIDTran is the Registration ID that is
used for license deactivation. A new RegIDTran is
automatically generated whenever the Activation Server generates the License
Key to respond to the license activation request.
The LicKeyTran is the License Key that is
sent from the protected application during the license deactivation request. It
contains the current license status of the application, including Key
Properties such as the execution count, enabled modules, and Key Data. When the
user activates the application again to retrieve the license, the Activation
Server uses the LicKeyTran to generate the License
Key in response to the license activation request.
The following field is used for software update subscription, when automatic software update is enabled in the
protected application. The Activation Server checks the SubscriptionExpDate
field to determine if the account subscription has expired. If the subscription
is valid, the protected application is allowed to download software updates
from the Update Server.
The SubscriptionExpDate field is also useful
for general account subscription (including when automatic software update is
disabled). For example, it shows the subscription expiration date for support
services you may provide.
The SubscriptionExpDate field shows the
subscription expiration date. It is calculated from the DefaultSubscrpPeriod
field in the Products table when a product is applied to the account. In other
words, SubscriptionExpDate is equal to the number of DefaultSubscrpPeriod days beyond the current date of the
server.
In addition, SubscriptionExpDate is
recalculated from the SubscriptionPeriod field in the
Upgrades table when an upgrade is applied to the account. If the subscription
has not expired, SubscriptionExpDate is equal to the
number of SubscriptionPeriod days beyond the current SubscriptionExpDate. If the subscription has already
expired, SubscriptionExpDate is equal to the number
of SubscriptionPeriod days beyond the current date of
the server.
See Also