3rd party plugin licensing capabilities
Answered
Hi,
How do you handle plugin licensing? I want to understand how I would guarantee that a customer pays for an individual license of our plugin, and how to enforce that programatically on our 3rd party plugin.
For example - seems like NxWitness already generates a unique Hardware ID (HWID). Can this be used by our plugin to implement our own licensing?
Alternatively, do you offer some plugin licensing support API/SDK or functionality already?
Thanks
-
Hello,
Nx Witness licenses are bound to a one or several HWIDs in the System.
You could request them with /rest/v2/licenses.
There are no technical restrictions for binding you licenses to those HWIDs,
Alternatively, do you offer some plugin licensing support API/SDK or functionality already?
There is not specific licensing support for plugin developers. It's up to developers how to implement licensing.
Could you share your ideas, what would you expect of such a licensing functionality?
1 -
Thanks for the question.
We will get back to you shortly.0 -
Could you share your ideas, what would you expect of such a licensing functionality?
Minimal functionality would be to allow to get a unique HWID via the NxWitness plugin API. Is this available at the moment?
0 -
Hi Bruno Oliveira,
There is an API for retrieving the HWIDs of a specific server. Please refer to the following URL:
https://{NxMediaserverIpAddress}:7001/rest/v2/servers/this/runtimeInfoYou would get the list of all HWIDs which are bound to the server, you can choose one of the HWIDs that has the prefix with 05 (i.e. the latest version of HWID, others are all used for the old version of Nx Witness for backward compatible)
Hope this helps.
0
Please sign in to leave a comment.
Comments
4 comments