Infralution Support

[Happs]

We have access to Licensing system (ILS) source and using the ILS in one of our new product. We are now considering to use the ILS in another product.

I have explained below how our existing product works, would like to get your option whether the ILS can be used. In our existing product, we provide following types of licenses:

Existing License system:

1. Unlimited license: User can install the product any number of machines and use the product to any number of accounts.

2. Limited license (2 types):

- Fixed number of accounts: For example, 100 users license. At this moment we don't have any tracking whether user uses more than number specified.


- Fixed names of the accounts: For example, user1, user2, user3, etc. User provide us accounts name, its hard coded to the license file. Our program will only operate accounts specified to the license files.

In any license type, user can install the program to any number of machines, we don't have any restrictions about this.

Using ILS:

License type 1 (unlimited) should not be an issue with ILS, we will provide unlimited license with max authentications set to large number. User have to authenticate when install in any machines, we can monitor how many times the license authenticate in License Tracker.

License type 2 (limited) need bit more thoughts and advice from you. Basically ILS need to transmit the account name, check against the list of accounts name. If the name exists then operate normally, if not then add to the list and check against max authentications number set to (e.g 100, 1000). If reaches the limit then we can warn user that number limit reached. There is a possibility of multiple machines authenticate same key but different accounts.

Hope this make sense. Do you have any advice about how we can achieve the License type 2 issue? Situation when our ILS server down for some reason and user attempt to authenticate, etc?

Thanks in advance for your suggestions.

[Infralution]

I'm not really clear on what you are trying to achieve with license type 2. You can include information (as XML or text) in the AuthenticationData for the license that the application can then read and then verify that the license is valid for what they are trying to use it for. This could for instance include a list of accounts the license is valid for.

If the authentication server is down (or the client doesn't have an internet connection) they can email you the license file to be authenticated by you manually using License Tracker. You then return the authenticated license file and they install it using LoadLicense. They can also authenticate the license themselves from another computer with an internet connection by visiting the AuthenticateFile.aspx page.
_________________
Infralution Support

[Happs]

Thanks for providing your thoughts.