TOKEN KEYS

A token is a specific license key used for activating software. There are two main types of keys:

• License Key
  • When a license is created, SLASCONE generates one license key and several (1:n) associated token keys. 
  • The license key can be used multiple times (n times) for activation.
  • Used for activation in floating device and named device scenarios.
• Token Key
  • A token key is a one-time use key that can only be used for a single activation. 
  • It is employed in scenarios where strict control over the number of activations is required.
  • Used for activation in named device scenarios.

Tokens manage and limit the number of allowed activations for licensing purposes. Exception: a floating license code can be used to activate as many devices as possible. 

If a customer has two installations (e.g., development and production environments), a license with two tokens is necessary. You can either use the license key twice or activate each of the two token keys individually.

GOODWILL TOKENS

Additionally, there are goodwill tokens that allow for a temporary exceedance of the licensed activation limit to mitigate customer dissatisfaction. These tokens create a "yellow zone" where the customer can continue to use the services even if the maximum number of devices has been exceeded.

Overall, tokens serve to manage the licensing and activation of software, ensuring that usage complies with the licensing terms.

SUSPENSION

If you need to suspend a device (Client-ID), please follow the guidelines below:

• Suspension Overview:
  • Suspending a device means that it will be temporarily inactive and unable to perform critical actions.
  • The suspension has a defined end date.
• Suspension Effects:
  • No Heartbeats: Heartbeats are rejected (409 Conflict).
  • No Session: Sessions can not be initiated or refreshed (409 Conflict).
  • No Activation/Deactivation: The device cannot be activated or deactivated during the suspension period.
•  API Response:
  • All API calls made by suspended devices receive a `409 Conflict` response, indicating that the client/device is temporarily suspended.

WHAT IS SUSPENDED

Although you technically suspend a token assignment, what is actually suspended is the underlying client_id.

This means that the installation with this client_id is going to remain suspended regardless of the used license key. This prevents installations from bypassing a suspension.

TOKEN STATUS

You can easily identify all suspended tokens by using the respective filter.

CLIENT/API CONSIDERATIONS

Use this API call to suspend a token (or to remove a suspension) from a token:

PUT /isv/{isv_id}/licenses/{licenseid}/assignments

Use the suspended_until_utc parameter to suspend a token temporarily.