Skip to Content
PortcullisDocs
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.

OnlineOffline (air-gapped)
NetworkOutbound HTTPS to the Portcullis API hostNone
ActivationEnter the license key; the product calls PortcullisProduct exports an activation request (.req); Digicom returns a license file (.lic)
File validity (exp)The lease (for example 30 days), never beyond the license endUsually the license end date
Renewal and changesPicked up automatically at the next check-inDigicom issues a new .lic; the operator imports it (no new request needed)
Suspension / revocationReaches the product as a signed file at the next check-inTakes effect when the current file runs out or a new file is imported
DeactivationFrom the product's admin screenAsk Digicom to deactivate the machine

Online

  1. The operator enters the license key in the product.
  2. The product calls POST /client/activate and receives a signed file.
  3. Every check_in_interval_hours the product calls POST /client/check-in and stores the fresh file. It also reports its version and usage.
  4. 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

  1. The operator clicks Generate activation request in the product and sends the .req file to Digicom support.
  2. Digicom staff upload it in the console and download a signed .lic file.
  3. 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).

On this page