License Revocation by End Users (Client-Side)

Client-side license revocation enables end users to revoke licenses directly from the machine where the license is installed. This capability supports license return and license rehosting.

End users typically revoke licenses in the following scenarios:

>Returning unused licenses or licenses that are no longer needed: Revoked licenses can be exchanged for a different product or returned for a refund, subject to vendor policy.

>Rehosting licenses to another machine: A license may be transferred from one machine to another when a machine change occurs, such as receiving a new laptop. For example, in enterprise environments, a system administrator might redistribute a revoked license to another office or division.

Prerequisites for Client-Side License Revocation

A product is eligible for client-side license revocation when all features in the product support the revocation operation. Features in a product can use different license model types, as long as each model type is eligible for revocation.

The following license model types support client-side license revocation:

>Perpetual

>Expiration Date

>Time period–based licenses, such as Time From First Use and Time From License Generation, supported only when the license has not been used

>Execution count–based licenses, supported only when the license has not been used

Client-side license revocation also requires the following conditions to be met:

>The feature has not expired

>The license is not detached

>The product is not cloned

>The Sentinel SL key is enabled

When any feature in a product does not meet these prerequisites, the product is not eligible for client-side license revocation. In such cases, the Transfer API returns status code 114 with the message HASP_REVOKE_NOT_ALLOWED.

A revoked product remains visible when queried by using the Sentinel Admin Control Center (ACC) or the hasp_get_info API. The API response the product with a revoked status set to TRUE. Any attempt to log in to a feature in a revoked product fails.

Client-Side License Revocation Workflow

To support license revocation, the vendor develops a license revocation tool using the Sentinel LDK Transfer API and provides the tool to end users to perform Step 2 of the license revocation workflow. In Step 3, the end user synchronizes the generated C2V file with Sentinel EMS through the Sentinel Customer Portal, where the revocation request is validated and the license capacity is recredited.

The client-side license revocation workflow includes the following steps:

Step 1: Prepare the License Revocation Tool

The vendor uses the Sentinel LDK Transfer API to build a tool that allows end users to revoke licenses from their machines. The vendor defines the design and interface of the client-side license revocation tool (for example, command-line, graphical user interface, or another format). The tool should be packaged and delivered to the end user with instructions on its usage.

Step 2: License revocation on the machine

After receiving the tool, the end user performs the following steps on the machine where the license is installed. The machine can be a local or remote machine.

1.Run the vendor-provided license revocation tool.

2.Initiate the license revocation for the relevant products.

3.After successful revocation, the tool generates a C2V file.

4. Save the generated C2V file.

Step 3: Synchronization with Sentinel EMS

1.Open the Sentinel Customer Portal login page.

2.Based on the license installation location, do one of the following:

•For licenses installed on a local machine, select Update/Sync Licenses Online to synchronize the revoked product licenses directly with Sentinel EMS.

•For licenses installed on a remote machine, select Begin Offline Update/Sync to open the Offline Update/Sync page.

Select the generated C2V file and click Submit to complete the synchronization with Sentinel EMS.

Sentinel EMS validates the revocation request and recredits the activation quantity to the corresponding entitlement. After successful processing, the license becomes available for reuse, reassignment, or redistribution.

For more details on the Customer Portal, see Guide to the Sentinel EMS Customer Portal.

Supported Protection Keys and Platform

Client-side license revocation supports the following protection keys and platforms:

>Protection keys: Sentinel SL AdminMode keys and Sentinel SL UserMode keys

>Platforms: Windows, Linux (Intel and ARM), and macOS