The CheckPoint License Server allows you to add central authentication / activation functionality to your application to deliver a truly world-class automated activation solution with a broad range of features.  Activation can be fully-automated.

The CheckPoint License Server is designed to receive calls from a variety of sources.  This includes web-service calls from  the ClientProtector running on your users system to automatically activate software on that users system by doing a code exchange.  A CheckPoint code exchange is different from other code exchanges because it involves a Serial Number (as well as an Authorization Request Code and reciprocated Activation Code).  Serial Numbers are tokens of ownership to some aspect of one or more copies of your software.

You will control automated activation of your software by interfacing with the ClientProtector run time component.  The ClientProtector takes care of all the details of binding to the web-service, details of communication including handling proxy servers and lets you deal only with the high level concepts and the user interface.

The ClientProtector logic allows you to respond to synchronous events to release Copy-Protection by means of a Serial Number code exchange. Alternatively you can make calls to the ClientProtector to invoke the CheckPoint Server to activate arbitrary functionality by means of a Serial Number.   

When you choose to provide automated activation for your software users, this does not preclude you from providing manual (by phone) activation in the same application. The most comprehensive solution provides both options to your users.

Chunked Responses Issues

The Microsoft Windows internet libraries that facilitate HTTP communication use settings that can cause issues with the CheckPoint License Server communication.  If you or your clients experience hangs while waiting for the CheckPoint Server to respond, have you client check the following Internet Explorer setting. (IE is the only way to graphically access this setting):

1. In Internet Explorer Tools / Internet Options / Advanced tab /

2. Make sure "Use HTTP 1.1" and "Use HTTP 1.1 through proxy connections" is checked - otherwise a chunked response may hang.  See the below image:

 

About SSL (HTTPS) and Proxy Servers

Keep in mind that proxy servers generally can not act as a proxy for HTTPS (SSL) communication.  HTTPS requires a secure handshake from point-to-point to enable its secure communications.  A proxy server can not be in between the two participants (client and server) of an SSL communication. Most enterprises that use proxy servers allow direct outbound SSL communication for the workstations (default port 443) to allow SSL communication to work.  If you are deploying your CheckPoint Server to be accessible via HTTPS only, be sure to take this into account when managing proxy server information.

More Information

For specific information on responding to the events that the ClientProtector fires at your application allowing you to release Copy-Protection using a Serial Number, see: OnPrepareAutoActivate.

For information on how to design your license to use CheckPoint Activation, see: CheckPoint Server Data Tab

For information on how to deploy your license on the CheckPoint License Server for automated Activation, see: Deploying License Projects on the CheckPoint Server