Multiple license users on the same device

Overview

When using user-based licenses, a user should be assigned per device due to limitations in our database model. For scenarios involving multiple users sharing devices, we recommend using a naming convention for HWIDs — for example, adding a suffix/prefix like station_hwid_user1. When a user operates locally, they can override the HWID with something like local_hwid_user1. When a user has max_activations = 1 this will lead to the user using either station_hwid_user1 or local_hwid_user1. This ensures that each HWID is uniquely associated with a single license user, preventing conflicts when multiple users (with different emails) are using the same machine.

The current flow is flawed because it relies on the hardware ID as the source of truth instead of the license user, which can lead to incorrect activation tracking and conflicts across shared devices. If your business logic uses hardware_id for additional checks be sure to always add the suffix/prefix.

Use a deterministic scheme that includes the username (or user identifier) in the HWID so each license user maps to a unique hardware identifier even on shared devices.

Platform

Create a user based license and assign license users to the license.

SDK flow

To support hardware ID overwrites, the system must use the HardwareID algorithm in combination with the username. In this example, we append the username as a suffix to the hardware ID:

example.cpp

config->setHardwareID(getHardwareId() + "_" + username);

Example Scenario

We enforce a rule where each license user is allowed only one activation, but a single device can host multiple license users simultaneously.

Example flows:

• User [email protected] activates their license on a local machine. This should:

  • Increment the license’s total activation count by 1.

  • Increment that license user’s total activation count by 1.

  • Assign the computed hardware ID as:

    • [email protected]

• Two users [email protected] and [email protected] sharing the same station machine under the same license will get distinct HWIDs:

  • [email protected]

  • [email protected]

This approach ensures that each license user has a unique hardware ID, even if they share the same physical device. As a result, license user-based activation tracking remains unambiguous, avoiding any inflated or deflated total_activation counts.

Switching Machines

1

Deactivate on the previous machine

User [email protected] must deactivate the license on the station machine before moving.

2

Activate on the new machine

User [email protected] then activates the license on the local machine.

The same rule applies when switching in the opposite direction — deactivate on the current machine, then activate on the target machine.