License Invalidation and Deactivation

License invalidation is the process of deactivating a previously validated license key, rendering it unusable on the current system. This single method performs two primary functions: it remotely invalidates the license on the server, making it unavailable for future use on the originating device, and locally deletes the associated saved license file or registry data.

For users holding a node-locked license, providing a straightforward mechanism for license invalidation directly from their device is especially important. This capability empowers users to deactivate their existing license, which then permits them to transfer it to a new device. This not only significantly enhances the flexibility of license management but also ensures that users can seamlessly migrate their software to new hardware without losing access to their licensed entitlements. Offering clear instructions and an intuitive interface for this deactivation process can substantially improve the overall user experience and reduce support inquiries related to hardware changes.

For users leveraging a floating license, the act of deactivation carries a distinct meaning: it signifies the release of a currently used license back into the central license pool. This action immediately makes that license available for another user on the network to acquire and utilize, ensuring efficient resource allocation and maximizing the concurrent use of the software within the licensed limit.

License invalidation or deactivation is accomplished with a single, straightforward call to the invalidate method.

// Invalidate/Deactivate previously activated license
License.getInstance()
        .invalidate() // deactivate previously activated license

The process of license deactivation has a distinct impact depending on the license type in use. When a node-locked license is being utilized, deactivation initiates the removal of the corresponding saved license file from the disk or the deletion of the relevant license data from the system's registry. This action effectively unbinds the license from the specific device.

In contrast, for floating licenses, the activated license data is not persisted on the local disk or in the registry because usage is managed centrally by the license server. Therefore, deactivation doesn't involve local file or registry removal. However, it's important to note that if a local floating license server is being used, the system may store the provided license key or the floating license server's address. This ensures that subsequent validation attempts can successfully connect to the server and re-acquire a license from the pool as needed.