matejskWe want to use LicenseLM (TurboFloat?) in limited hosted environment. This means that we only have access to REST APIs. We cant use any of provided libraries.As environment is highly managed, we dont need features as hardware locking. Our only identifier is sort of tenant ID. We want to call LicenseLM API to activate and manage our AddIn within SaaS solution.
Much more information is needed. Likely the NodeJS integration would be the best fit for you. But hard to tell. Not quite sure what you're trying to do. If it's completely on your own servers then just create a login system.
If you're selling software that will be install on other people's systems, then yes, you'll need hardware-locked licensing.
https://wyday.com/limelm/help/licensing-types/
https://wyday.com/limelm/help/using-turboactivate-with-electron-nodejs/
matejskHi,Thank you for reply. Our add-in is hosted within providers application. Login system is already implemented by managed SaaS platform (like hosted CRM). We would like to add user licensing (not necessarily named user concept). Like customer buys 50 user pack. From the provided link I think best match is Floating license mode.
As we cant add any external library and programming language is very limited (custom language OOP and REST methods are supported) my first idea was to call LicenseLM API but this is for management. Also, its not possible to run any executable within add-in.
How do you support .NET core? Only native support without platform dependant executables solution would be acceptable.
Yes, we support .NET core: https://wyday.com/limelm/help/using-turboactivate-with-csharp/
Can you please answer / debate first part of previous post?
What you are mentioning is .NET Framework - this is now stale.New framework is called .NET Core (current version is 3.1) and it's platform independent. How do you plan to support this?
I did some analysis of NodeJS implementation - it's again dependant on platform specific systf.exe.Where is API specification for license "consumption" part. Only API documentation for administrative operations is published.
.NET Framework / .NET Core are functionally identical. Different branding for same thing. (Yes, the technical details are different, but long story short: it works, trust us).
TurboActivate / TurboFloat are dependent on the system. That's by design. It's covered extensively in the documentation:
https://wyday.com/limelm/features/why/
https://wyday.com/limelm/help/licensing-types/
There is no way to work around that. If you want to integrate TA / TF in your app then you need to use one of the integration methods provided.
Like I said earlier, it looks like what you're actually looking for is a login type system, not a licensing system.
We provide licensing systems.
