Is it possible for the user to deactivate their own licenses once they are lost?

Hi,

Some of my users run into the following problem:

1)they activate the software;2)something happens and they lose access to the computer (they re-install Windows, kill the VM, lose the computer etc.)3)they need to activate the software again;

When that happens they email me and I deactivate it for them so they can use it again. Unfortunately this is not very practical longterm solution. Is there any way for the users to access their license and deactivate an activation to use it again?

Well, for cases like virtual machines (of all types), web hosting where the "host machine changes (like AWS), terminal services, and times when a company needs a "pool of licenses" to draw from, you'd use TurboFloat Library and the TurboFloat Server. So, that's the solution to those problems.

Regarding letting the user "remotely deactivate" themselves is a security risk. You don't want it because it means a customer could install your app on as many computers as they want. You could always implement it yourself using the web API, but I wouldn't recommend it.

Thank you, I thought it's not possible, just wanted to make sure.My customers are private individuals (not companies) but many of them travel a lot and that leads to all kind of problems where deactivation from their side would be useful after the fact (I let them call deactivate if they want).

>> You could always implement it yourself using the web API, but I wouldn't recommend it.

That would mean distributing my private API key to all the customers, right? (in the compiled binary but still).

I think Wyatt means that you could create an API sitting on your servers that interfaced with LimeLM's web api. So, no you wouldn't need to distribute your API credentials to the end user. Just setup a webpage that has server scripts that communicate to LimeLM.

Right, thanks for the suggestion. For now it's not worth the hassle for me to maintain a separate service just for that but it might be in the future 🙂

Reply
Discard post