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 adding an air gapped license with the api 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 add airgap license docid\ gvftipqb5ljyzzjqchlxq adding an air gapped license with user interface air gap license activation on ui generating activation code 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 activating license on client side 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 docid\ gu7iu9oliugdxxm yuxw