SDK Glossary

anti clock tampering anti clock tampering incorporates inherent logic to detect any alterations made to the local machine's time in an attempt to circumvent license policies this mechanism helps maintain the integrity and enforcement of license terms and conditions within licensespring, a timestamp inside the local license file is saved every time a local license is saved during the local license check the sdk will compare the current system datetime with the timestamp from the local license if the current datetime is older than last timestamp, the sdk will throw an exception, such as clocktamperedexception this exception can only be thrown only during local license checks, and would not apply to online license checks device variables device variables are key value pairs defined by the developer, which can be stored on the local computer and sent to the licensespring platform using the senddevicevariables function these variables provide additional information or context about the device and can be used for various purposes within the licensing system device variables platform location floating client the floating client docid 85ozdmi ceei i5t6ldh7 module focuses on providing floating license features it handles the management and usage of licenses that can be shared among multiple users or computers license client the go license client docid 49m1mya9tar5rnzoc5hvf module implements essential license functions such as online and offline license activation/deactivation, trial licenses, consumption tracking, and variable management license activation activate license (online method) docid\ mt2ygm6cjzh2bumu gfww refers to the process of entering the license key into the application, unlocking the associated entitlements by activating a license key, users can access the full version of a trial application or enable additional features activation starts both the validity period and the maintenance period associated with the license key depending on the product's configuration, a license key can be activated on one or multiple computers license check check license docid\ zh4kfih s59tzibzkeb9o refers to the process of refreshing the local license file with the latest entitlements stored on the licensespring servers in the event of an exception, the license check can provide descriptive information about any problems that occurred additionally, it is possible to perform a local check on the device without connecting to the backend this local check is useful for verifying the validity of a license and detecting any tampering attempts, triggering an exception if any issues are detected license deactivation license deactivation involves unbinding the device from the license and reducing the total activation count the specific outcome of deactivation depends on the license transfer policy in place typically, deactivating a license frees it up to be activated on a different device, allowing for license mobility and enabling the license to be utilized elsewhere license files when a license is activated, the sdk generates a license file on the user’s machine this file contains encrypted license information and is required for validating the license locally the type and location of the license file depends on the activation method local license file after an online activation, the sdk automatically creates an encrypted local license file this file is managed by the sdk and ensures that license checks can be performed without requiring a constant internet connection the exact location of the file depends on the operating system you can find detailed instructions on where to locate the license file in your environment in the local license file docid\ fkfzhha n838tznrzu0sz offline license file for environments without internet access, licenses are handled using offline activation files in this case, the first step is to generate an offline activation request file, sometimes referred to as an offline license file this request file is then submitted to the licensespring server to obtain a matching activation response file, which completes the offline activation process detailed instructions for this workflow are available in the offline activation guide license policy file our software is deployed together with a license policy file, which defines the licensing rules for the product this file is shipped with the application and serves as the foundation for license activation instead of relying on direct http requests or manual file exchanges, activation occurs through a series of code exchanges that bind the license to the license policy file in practice, the license policy file is always included with the product, and when a license is activated, it simply follows the terms defined within that policy this file is used exclusively for air gapped licensing docid\ cgpsvoymm4d4c4iohilhs scenarios , where internet connectivity is limited or unavailable licensefilepath licensefilepath refers to the file path location where the local license is stored on your system license management license management is a java management sdk docid\ oqehm3fli2mj 0aq8u724 module that offers apis for generating license keys and placing orders it facilitates license key management, including creation, modification, and order processing floating cloud license floating cloud license is managed entirely through the licensespring cloud platform each client activates against the platform and checks out a license when the application starts this model requires internet connectivity for license checkout, although licenses can be borrowed for temporary offline use it supports concurrent usage across multiple users and machines, provides real time monitoring, centralized management, and detailed reporting this makes it ideal for distributed teams and organizations that require flexibility and visibility floating server license floating server license is managed locally through a license server hosted in the customer’s environment clients check in and out licenses from the local server without needing constant internet access, making it suitable for offline, restricted, or air gapped environments while it offers more control over deployment, reporting is limited to local exports unless synchronized with the cloud, and it does not provide the same level of real time monitoring as the cloud based model hardware id hardware id is a unique identifier assigned to a device and used to activate a license it links a license to a specific device, preventing unauthorized transfer or use the licenseapi and licensemanager use the hardware id module to generate a unique fingerprint for each device the default algorithm collects key device specific attributes and combines them into a single identifier, ensuring that licenses are securely tied to legitimate devices the algorithm works across different operating systems, abstracting hardware details into a consistent, unique string per device this approach balances security and usability, providing reliable license enforcement without requiring manual configuration detailed explanation of device id algorithms and implementation guidance, please refer to the hardware id documentation virtual machine detection virtual machine (vm) detection is a feature that identifies when an application is running in a virtualized environment it helps enforce licensing rules by preventing unauthorized duplication or use of software on virtual machines vm detection is useful for protecting your application but may need to be disabled in certain scenarios, such as testing or development environments, to avoid interfering with legitimate use as an alternative, hardware key self provisioning can be used to bind a license to a unique hardware identifier, providing a reliable way to prevent app duplication even when vm detection is turned off detailed guidance on vm detection and hardware key self provisioning, see the virtual machine detection doc