Is there a way to keep syncfusion license key hidden or encrypted when source shared with a client. Can the client reuse the same key for their own projects?
Hi Ponejai,
Q1) Is there a way to keep syncfusion license key hidden or encrypted when source shared with a client.
A1) As of now, we don’t have any option to secure the license key from exposing. We have implemented this licensing (key) validation system to avoid using our products inadvertently, so there is no need to add it in a secure way.
We are just using this licensing concept to prevent customers from using our controls without their knowledge.
So, you can directly use license key in your code for your internal development works\publishing your application to production.
Q2) Can the client reuse the same key for their own projects?
A2) If you are trying to use our components and would like to push your source to a public repository\or any open-source repositories or sharing you source project to your customers, you should not push\provide your Syncfusion license keys publicly along with your sources. You should push\provide your source without Syncfusion license keys.
You can inform the users to sign-up to us (Syncfusion) and get a trial or valid license to use our products.
You can distribute your deployed applications, but you shouldn’t distribute our license keys in a public environment or through your sources.
Please let us know if you’ve any queries.
Regards,
Jeyaseelan M
Thanks for your reference
Wha is the purpose of optional "Project" text box when downloading the License Key. Is that used to bind the key to a specific project so it can not be used by another project?
Thanks & best regards,
Also can not see Lincense Enabler tool download link anymore or with Syncfusion Control panel...
Ponejai,
License Enabler is a tool used to enable a license for your project(s)
We do not use this tool in the latest version as We have introduced a new
licensing system starting with version 16.2.0.x release of Essential Studio.
Refer to this link for more information’s about license key,
Overview of Syncfusion license and unlock keys - Syncfusion
Refer to this link for generating license key,
https://help.syncfusion.com/common/essential-studio/licensing/how-to-generate
Refer to this link for registering license key,
https://help.syncfusion.com/common/essential-studio/licensing/how-to-register-in-an-application
If the license key is not properly
registered, the below license errors will be displayed.
https://help.syncfusion.com/common/essential-studio/licensing/licensing-errors
Could you please let us know what you are trying to use?
Trying to use ASP.Net MVC EJ2 in one project. Since I have to share the source code, I do not want the reuse of Key in the code base by the client. So it is possible to reestrict the key to a specific project,so that it can not be reused in any other project?
My problem is this line
Syncfusion.Licensing.SyncfusionLicenseProvider.RegisterLicense("YOUR LICENSE KEY");
Since the code is shared with the client, he has access to my key and can reuse in other projects. Can I generate & restrict the key to a specific project. I was interested as I could see an optional Project Name in the generate license window..
thanks & best regards,
Ponejai
Attachment: lic_dd6a738f.rar
Hi ponejai,
There are no project-specific restrictions for generating the license key. You couldn't cancel, invalidate, or restrict the generated keys on your side. If you generate Syncfusion keys from the valid purchased license section, those Keys will not expire, cancel, or invalidate until your license period. Currently, there is no support for project-specific restrictions on the Syncfusion License keys.
Regards,
Kaviyapriya
but does a key generated for a specific version of Syncfusion works for another version? like downbloaded and generated for 20.3.0.60, will it work on both 20.4.0.50 & 21.1.35 & 20.2.0.50
Ponejai, no, the license key for v20.3.0.* will not work for v20.2.0.*, v20.4.0.* or v21.*
Syncfusion license keys are version and platform specific. So, you need to generate and register the license key for every new volume releases.
Example: 20.2.0.*, 20.3.0.*, 20.4.0.*, 21.*
You do not need to update the license key on a regular basis for
every weekly, patch or service pack releases. You need to update the license key in your
project for every major volume release upgrade
only.
Syncfusion will have only four major releases (Volume releases) in a year. So,
you might have needed to change the license key four times in a year.
Refer to the below KB article to know which version license key should use in
the application,
https://www.syncfusion.com/kb/8951/which-version-syncfusion-license-key-should-i-use-in-my-application