Multiple Licenses, Same Machine

General
#1

Similar to this post: https://cryptlex.com/forums/discussion/49/handle-different-users-on-same-machine-and-license-activations#latest

I understand the concept of node locked licensing. Hardware fingerprint/signature is the driver. Makes total sense most of the time.

Our programs actually reside inside of another product (separately licensed) that runs on a multi-tenant server, meaning some companies on the same server will activate our application and some will not. We can’t have one customer activating it and then having other customers access it because it’s on the same machine.

I am not clear on if the process of adding a custom field, Database Name for example, would force a new license key to be generated. I understand how the concept of restricting it to a single user (database) on the server would work, but how would a new license key be generated if I wanted a second user (database) to be activated on the same server with a different key? Or is this not possible? Ideally this would work for both trial and real activations.

Hope that makes sense.

#2

Hi,

As far as I understood your problem, you want to prevent access to same application installed on computer for different users.

If your second user has it’s different account in the OS it can’t use the key generated for first user as the custom field for the first license key contains the name of first user. So it would need another key with custom filed containing the correct value.

#3

How do I do that with a trial, given that the key is the same for all instances?

#4

Restricting trial to one user is not possible as once the verified trial expires, it will expire for all the users simultaneously, even if your customer reinstalls the OS it will still show expired.

In this case you will have to implement trial feature using custom fields.