How to secure license key
We would like to inform you that the license key is already secured. Development license key is applicable to your local host environment only. Production key is tied up to your domain name and therefore cannot be used by anybody else. Please let me know if you need more details about this.
I think I did not explain what I was asking.
Right now you can see the license key from the code, if I am the external person who has valid login to our company’s application, can login and copy the key and download the free trial from the flex website and use this key.
How to avoid this ?
Yes, the external person can easily copy the license key from your website or from the website of any other our customer. But your license key will not work on other domains because it’s strictly bound to your domain name. The component will say something like: “Sorry, it’s a wrong key for this website”.
Does it answer your question?
Actually its not. Sorry but I am not getting when you say “it’s strictly bound to your domain name”, what does it really mean ?
I copy the license key and then from any computer download the free trial of flex, and put that key as license. And that computer is not connected to internet anymore. I will be able to see the flex in the browser right, is there something in the code which will stop it ? What is domain in such situation ?
I think I understand your confusion. Now you have only development key and can copy it from one application to another. It will work until you try it on the real domain like http://www.fisglobal.com. It will say: “Sorry, it’s development key. You can’t use it on the real domain”.
All production license keys are bound to the domain names. Let’s say you use the component on http://www.fisglobal.com and have a special production key for this domain. If someone copies this key and tries to use on http://www.mydomain.com the component will say: “Sorry, this key is not applicable for http://www.mydomain.com“.
Please find more information here: http://www.flexmonster.com/doc/managing-license-keys/
Sorry one more query:
How do we deploy this to a customer? There won’t be a public domain, and there is a good chance that the server won’t even have internet access. We will likely have multiple environments at the customer site (UAT, Staging, PROD). Our applicatoin may be behind a load balancer that owns the domain (instead of the box it is actually on).
It depends on licensing model that you choose.
- For the single corporate license (SCL), you have one production key for deployment. Also, we can provide separate keys for UAT and staging but it still counts as one license.
- For SaaS model, you have production key for one domain and all subdomains. For UAT and staging keys, you have the same policy as in the SCL model.
- The OEM license allows you to have 10 production keys with UAT and staging keys for each domain.
- The unlimited license provides you with the unlimited number of keys for any desired domain name. However, these keys can be provided exceptionally for the domains that using your application, but not to 3rd party tools and websites.
I hope it helps 🙂