Concepts
Online vs offline
The two ways an installation gets its signed license file.
Both modes end with the same thing: a signed license file stored in the product's data directory, bound to the machine's fingerprint. They differ in how the file arrives and how it is renewed.
| Online | Offline (air-gapped) | |
|---|---|---|
| Network | Outbound HTTPS to the Portcullis API host | None |
| Activation | Enter the license key; the product calls Portcullis | Product exports an activation request (.req); Digicom returns a license file (.lic) |
File validity (exp) | The lease (for example 30 days), never beyond the license end | Usually the license end date |
| Renewal and changes | Picked up automatically at the next check-in | Digicom issues a new .lic; the operator imports it (no new request needed) |
| Suspension / revocation | Reaches the product as a signed file at the next check-in | Takes effect when the current file runs out or a new file is imported |
| Deactivation | From the product's admin screen | Ask Digicom to deactivate the machine |
Online
- The operator enters the license key in the product.
- The product calls
POST /client/activateand receives a signed file. - Every
check_in_interval_hoursthe product callsPOST /client/check-inand stores the fresh file. It also reports its version and usage. - If Portcullis is unreachable, the product keeps running on the current file and retries. Only when the lease and the grace period have both passed does it switch to restricted mode.
Offline
- The operator clicks Generate activation request in the product and sends the
.reqfile to Digicom support. - Digicom staff upload it in the console and download a signed
.licfile. - The operator clicks Import license file in the product.
The request file contains a random nonce that the product remembers. The returned file echoes it, which proves the file was made for that request.
See Offline activation (operators) and Offline activation (integration).