Air-Gapped

Air-gapped licenses are essential for systems that operate in secure or isolated environments without access to the internet. Below, we detail the processes for generating an airgap signature and adding an airgap license using the Floating Server API.

It is important to understand the workflow of air-gapped licensing prior to this guide, please see our documented workflow and ensure this makes sense before continuing.

Specifically, the use of the floating server affects steps 4 and 7 only. Steps 1-3, 5, 6 do not change.

This endpoint is used for activating the air-gapped license on the client-side, the final step of the air-gapped activation process. For more information on this API endpoint, see our API page for adding air-gapped licenses.

Rather than completing this step in the client application, as explained on our main air-gap page, we enter this information and receive our activation code on the Floating Server. This process is seen on the left side of the above screenshot.

Rather than doing this on the SDK, the final step in the activation of the air-gapped license is inputting the confirmation code and activating it on the client-side. This is done on the right side of the above screenshot.

A full step-by-step guide on activating air-gapped licenses on the floating server can be found at Air-Gap License Activation.