Air-Gapped License Policy
Air-gapped licenses allow ISVs to node-lock licenses on computers in air-gapped environments, where files are not allowed to leave the network once the software application has been deployed.
Instead, the software is deployed alongside license policy files, which can then be selected, and node-locked through a series of code exchanges (instead of http requests or file exchanges).
On the product page ( saas.licensespring.com/{companyID}/products/{productID} ) go to license policies tab and click on a add license policy button.
To mark policy as air-gapped switch the set as air-gapped switcher under the title to true.
You can either download the license file from the product license policy, or, if a license was set as "air-gapped", you can download the license policy file from the license detail page.
The air-gap portal for license activation is available on this public URL: airgap.licensespring.com
Process of activation is done in 4 steps including actions on server (portal) and SDK:
To start the license activation process, the user needs to enter the license key on the portal to initialize the air-gap license activation. This will create a one-time initialization code.
The initialization code needs to be imported to the SDK alongside with the license key. The SDK will verify the initialization code and return the activation code and hardware_id.
The initialization will generate a QR code containing the JSON with a license_key and an initialization_code included. This can help and remove the need for copy pasting or manually entering the codes.
When attempting to activate an air-gapped license, the SDK should be configured to activate activate an Air-gapped license. It will accept the license_key as well as the initialization_code and return the hardware_id as well as an activation code along with the license key. Go back to the air-gapped portal and click on "Enter air-gap activation code" and enter them in order to receive a confirmation code.
The license key, hardware ID, policy ID and this new signature confirmation code need to be input into the SDK. The SDK validates the code using company account public air-gap key which is also previously embedded in to the SDK. If successful, the SDK will use the policy ID to retrieve the license entitlements and use this as a local license file.
Generated QR code contains the JSON with license_key, hardware_id, policy_id and confirmation_code included which you can scan and then send or save. This can help and remove the need for manually copy pasting the codes.
