Blacklisting lets you stop issued licenses from working in future versions of your application, normally to allow users to move licenses from one host to another. Blacklisting applies to a specific feature in the license file, based on the unique KEY value of the feature.
You can use blacklisting for local, network and borrow licenses. Blacklisting of a network license must be done on a license server machine.
When a blacklisted license is checked out and is then checked back in, the feature will thereafter be unavailable for checkout. For blacklisted local licenses, checkout attempts will result in the message "Feature is blacklisted." For blacklisted network licenses, checkout attempts will be treated as if the feature does not exist, resulting in the message "Feature not found."
When replacing a blacklisted license file with a newly generated license file (re-hosting), the feature will be available for checkout again.
To blacklist and re-host a license:
- To revoke an existing license, set the LMX_SetOption flag LMX_OPT_BLACKLIST.
- To re-host a blacklisted license, replace the blacklisted license file with a newly generated license file.
Using the new license file, the feature will once again be available for checkout. Blacklisting can be verified using the end user utility lmxendutil, which can print out a list of blacklisted licenses.
Note: To replace one license with another license, you can also use the REPLACES directive. If network server re-hosting is frequent, you can manage re-hosting in a different way, such as locking the license to a dongle (see HostID values).