Closed r-brown closed 1 year ago
The above scenario can be configured in NetLicensing using two licensing models - Node-Locked and Subscription.
where the Subscription model can specify the default package (e.g. 7 days) to be automatically assigned for every new customer:
... and Node-Locked model can specify 1 default node:
Customer validation request will request both product modules at once:
curl -X POST -H "Authorization: Basic ..." -H "Accept: application/xml" \
-H "Content-type: application/x-www-form-urlencoded" \
-d "dryRun=true&productModuleNumber=M7ARR47QI&nodeSecret=device-fingerprint0" \
https://go.netlicensing.io/core/v2/rest/licensee/CUSTOMER-ID-01/validate
... and deliver the below response:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns2:netlicensing xmlns="http://www.w3.org/2000/09/xmldsig#" xmlns:ns2="http://netlicensing.labs64.com/schema/context" ttl="2023-01-06T07:43:09.232Z">
<ns2:infos/>
<ns2:items>
<ns2:item type="ProductModuleValidation">
<ns2:property name="productModuleNumber">M7ARR47QI</ns2:property>
<ns2:property name="valid">true</ns2:property>
<ns2:property name="productModuleName">Servers</ns2:property>
<ns2:property name="warningLevel">GREEN</ns2:property>
<ns2:property name="licensingModel">NodeLocked</ns2:property>
</ns2:item>
<ns2:item type="ProductModuleValidation">
<ns2:property name="productModuleNumber">MQQ9MC6HJ</ns2:property>
<ns2:property name="valid">true</ns2:property>
<ns2:property name="expires">2023-11-18T14:23:34.952Z</ns2:property>
<ns2:property name="productModuleNumber">MQQ9MC6HJ</ns2:property>
<ns2:property name="productModuleName">ABO</ns2:property>
<ns2:property name="warningLevel">GREEN</ns2:property>
<ns2:property name="licensingModel">Subscription</ns2:property>
</ns2:item>
</ns2:items>
</ns2:netlicensing>
valid
parameters from both ProductModuleValidation
sections need to be parsed and product behaviour is driven accordingly.
Question 2
is there a way to uninstall a node via API, for example, if the customer uninstalls our software on a computer?
It is possible to release node locking via API - as described at #30
It is also possible to allow customers to maintain their licenses by themselves via NetLicensing Customer Portal. So, customers can release paired nodes without involving the vendor's customer support.
Question