Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Combine Subscription and Node-Locked models in one product #58

Closed
r-brown opened this issue Dec 30, 2022 · 2 comments
Closed

Combine Subscription and Node-Locked models in one product #58

r-brown opened this issue Dec 30, 2022 · 2 comments
Labels
question Further information is requested

Comments

@r-brown
Copy link
Member

r-brown commented Dec 30, 2022

Question

We would like to map the following license models in the same product:

  • Subscription model (7 days free, then 1 year for a license fee)
  • Node-locking (customer can install our program on 1 or 2 computers (e.g. identified by CPU serial number) during the subscription period).

Is it possible to map this model in NetLicensing? If so, is there a way to uninstall a node via API, for example, if the customer uninstalls our software on a computer?

@r-brown r-brown added the question Further information is requested label Dec 30, 2022
@r-brown
Copy link
Member Author

r-brown commented Dec 30, 2022

Configuration

The above scenario can be configured in NetLicensing using two licensing models - Node-Locked and Subscription.

Screenshot 2022-12-30 at 08 42 47

where the Subscription model can specify the default package (e.g. 7 days) to be automatically assigned for every new customer:

01

... and Node-Locked model can specify 1 default node:

02

Validation

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 ProductModuleValidationsections need to be parsed and product behaviour is driven accordingly.

@r-brown r-brown closed this as completed Dec 30, 2022
@r-brown
Copy link
Member Author

r-brown commented Dec 30, 2022

Question 2

is there a way to uninstall a node via API, for example, if the customer uninstalls our software on a computer?

Option 1 - API

It is possible to release node locking via API - as described at #30

Option 2 - Customer Portal

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.

@Labs64 Labs64 locked and limited conversation to collaborators Oct 30, 2023
@r-brown r-brown converted this issue into discussion #109 Oct 30, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
question Further information is requested
Development

No branches or pull requests

1 participant