Rehosting or blacklisting a license - X-Formation Knowledgebase

Search the Knowledgebase	Browse by Category or Article ID
[Advanced Search]

Rehosting or blacklisting a license

Would you like to...

Print this page

Email this page

Subscribe me

del.icio.us

Digg it

Export to PDF

User Opinions (0 votes)

No users have voted.

Article ID: 193

Last Updated: 19th June 2009 08:40:36 pm

The following example describes how to re-host a user's license or deny a user the ability to use a particular license. You can use unique id, serial number or hostid.

Add the particular blacklisting id into the security configuration file (vendor.lmx) and then recompile the distribution to ship the next version of the software with an updated lcodedata object.
Build a menu point into your application that temporarily stores the serial number, hostid, or unique id in a file on the user’s hard disk; for example, using client store. Note: The user’s license includes a serial number or a hostid, which is know at license creation time. If you want to use the unique id, ask the user to give you their unique id, which can be obtained using LMX_GetFeatureInfo().
Upon checkout of licenses, call LMX_GetFeatureInfo(), and compare the serial number, hostid, or unique id with your local blacklist file. This step will immediately stop the license from working.
Release a new version of your application sometime in the future with the blacklist information included.

Note that local temporary blacklisting is not practical for network licenses shared by several users, because the blacklisting is performed only on a particular machine.

If network server re-hosting is frequent, you can manage this in a different way, such as locking the license to an LM-X compatible dongle, as described in Hostid values in the LM-X Developers Guide.

For detailed information on client store and API function information used in this example, see the LM-X Developers Guide.