JLicensure™ Features
Simple-to-use
A well-documented programming interface lets you easily include the JLicensure client library in your software. Just a few lines of code are necessary to let JLicensure check the validity of the software license... in any part of your code and as often as you like during the execution of your program.
Firewall-friendly
JLicensure was specifically designed to work through restrictive firewalls to minimize activation problems for a broad mass of end-users by using the HTTP protocol to communicate with the JLicensure server.
In addition, JLicensure comes with a special set of proxy modules that allow both the server and the client to reside behind firewalls that do not allow TCP connections from the outside.
Transparent
Understandably, most end-users do not want the software they are running on their machine to perform unauthorized data transmissions to some other host on the Internet. Software that sends data that is unverified by the user could be suspected to be participating in some sort of data-mining, i.e. collection of (possibly personal) information (so-called „spy-ware“).
This is why we designed JLicensure to be as transparent (that is as open and controllable in respect to the end-user) as possible. If the JLicensure Client Module needs to download a license from the server (this usually happens only once during installation or start-up), the user has full control over the process. All information is transmitted in clear-text and the user can preview the complete data before it is sent.
Secure
JLicensure uses state-of-the-art cryptography to digitally sign and verify the licenses granted by the server. You can of course select algorithm type and key lengths according to your needs.
The JLicensure client library is protected against modification by
our JarCryp Technology
. Even though it is not necessary, it
is highly recommended to integrate the JLicensure client library with your software and encrypt the
whole software by using the JInstaller Secure Edition
.
Automatic
The validity check of licenses is an automatic process. Every time you call the license check routines in your code, the JLicensure Client Module automatically loads and verifies the appropriate license. For this matter, all licenses are backed up in a local persistent storage (Java Preferences) to be instantly available for revalidation. If a license is not yet (or not anymore) available in the local storage, the process to request and download it from the server is automatically initiated.
Flexible
All parts of JLicensure are highly customizable. The server, for instance, was designed to work with any type of relational database that can be accessed via JDBC without demanding a specific table or column structure to store the licensing information. Thus, if you wish, you may configure JLicensure to use your own existing database that may already contain your client's customer data or software serial numbers or whatever. The server automatically maps the information in a license request to database table columns. You are completely free to define how a license actually looks like and what information you want to store in conjunction with a license.
Since all parts of JLicensure are based on interface specifications, you are also free to replace any part of JLicensure with your own implementation. This means you can customize specific parts of JLicensure to fit your needs.







Send Article
Print

