End User Offline Activation

Zentitle2 fully supports offline activations, enabling your customers to activate a seat when the machine has no internet connection.

Note that an application that has been activated in an offline node lock manner cannot use the Advanced Features (usage count, element pools).

Applications using the Local License Server can make use of all Advanced Features.

Note that the End-User Portal is required to manage the activation request and retrieve the token. It is similarly required for offline deactivation.

The API calls to manage offline activations are in the Management API, and there are functions to manage offline activations within our client SDKs (for example, our .NET client).

Activate an offline machine.

Using the client SDK, generate an offline activation request token within your application and move it to a connected machine (such as using a USB key, copy/paste, or other technique). See Step (1) above.

In order to test this, you will need an activation code associated with the product and entitlement tested. This can be found in the "entitlement" section in the Zentitle2 UI.

Transfer activation request to the offline portal page

Now, you need to access the "end user portal" page related to your account.

In the real world, this would be the specific end-user portal page for your specific customer.

This will activate a seat against the entitlement in the Zentitle2 cloud and generate an Offline Activation Response Token.

Use the offline token with the "offline" machine to activate

Go back to the offline machine (Step 2) and use the client SDK to ingest the response token in order to complete the offline activation sequence.

The offline machine is now "activated" with the required entitlement.

Deactivate an offline activated machine.

Similarly, a user can de-activate an "offline activated device" by calling the DeactivateOffline API in the client SDK, which will immediately invalidate the locally cached license and simultaneously generate a Deactivation Credit token, which can be copied/moved to a connected machine using a USB key or other means and pasted into the End User Portal in the 'Deactivation' section.

Deactivate an offline machine.

Using the client SDK, generate an offline deactivation request token within your application and move it to a connected machine (such as using a USB key, copy/paste, or other technique). See Step (1) above.