How it works
The classic flow has four steps.
- The app on the offline machine shows a request code. It contains the license key and the machine’s fingerprint.
- The customer types or scans that code on a connected device, usually a web page.
- The server checks the key, counts a seat and answers with an activation code signed with the vendor’s private key.
- The customer enters the answer in the app, which checks the signature with a public key built into the app.
It exists for air-gapped machines, which are kept off every network on purpose.
Typical failure modes: a typo in a long code, a request code that expires before the customer reaches a connected device, and a fingerprint that changes after the code was issued so the response no longer matches the machine.
Offline activation versus offline verification
These are often mixed up. Offline activation answers “may this machine be registered”. Offline verification answers “is this license still good” using a signed token the app already holds. The second needs one online call earlier. The first needs none on the device itself.
How Clavem handles it
Clavem has no challenge-and-response flow. Activation is a call to POST /v1/licenses/activate, and the response includes a token signed with the product’s Ed25519 key. The app verifies it with the public key and needs no network afterwards.
The token has a clock. It carries iat, when it was issued, and refresh_by, which is iat plus 14 days. A real token from the demo license had iat 1795126812 and refresh_by 1796336412, a difference of 1,209,600 seconds. Your app trusts the token until refresh_by, then asks the customer to connect once.
What an air-gapped customer needs from the seller
These are patterns the seller builds in the app. Clavem does not ship them.
- One connected step. The offline app shows its fingerprint. On any machine with internet, a small tool or web form of yours calls
activatewith the customer’s key, that fingerprint and a device name. The token that comes back carries the fingerprint asfp. - Carry the token across. The customer copies the token to the offline machine. The token is not bound to a device, so the app should compare
fpwith its own fingerprint before trusting it. - Pick a window.
refresh_byis advice to the app, not a server rule. A seller serving a sealed lab can decide to keep trusting a verified token for longer, or to accept a new carried token every 14 days. The cost of a longer window is that a revoked license keeps working on that machine until the next token arrives.
Tell buyers the real window. An app that follows the documented flow asks for a connection once refresh_by has passed. See signed license tokens for the fields, and the offline verification docs for working code in five languages.
Questions
Is offline activation the same as offline license verification?
No. Offline verification checks a signed token with no network after an online activation. Offline activation registers the device itself without the device being online.
Can Clavem activate a machine that is never online?
Not by a built-in flow. Activation is an API call. A seller can build a carry-over step in the app, described below, and decide how long to trust the token.