WebLM supports client node locking of licenses where licenses are tied to specific application instances. You cannot move licenses across application instances. The feature is provided to support some Avaya data products that require licenses to be node-locked to an application instance or the client. For example, VPFM/COM. To use this feature, you must include the host IDs of the application instance and the WebLM server in the license file.

With the client node-locking feature:

• WebLM allows multiple licenses for a client node-locked product to be installed on the server at the same time. Each client node-locked license contains a unique host ID of the client.

• When a client node-locked license is installed on WebLM, WebLM automatically associates the license file with the client or application host ID that is included in the license file.

• The license request from the element would include the client/element host ID. WebLM serves licenses only if the client host ID in the request matches with any of the installed client node locked license files.

• WebLM enforces mutual TLS authentication for client node-locked licenses.

• The license over-install checks are based on the client host ID. While over-installing a license file with a new file for a client instance whose client host ID changed due to rehost, license file includes the old and new client host IDs. In this case, over-install check will be based on the old client host ID.