When purchased, our Qlik products are delivered with a 16-digit license key. How that key is applied may differ depending on your requirements or the version of the product.
We’re here to tell you a little about that.
Generally, you’ll have two activation options:
The Signed License key (SLK), available for Qlik Sense, and ABDI.
And a combination of the 16-digit key, a control number, and the License Enabler File (LEF)
Note: These license activation methods cannot be mixed. A license activated with an SLK cannot also be activated using the key + control number method.
Customers who have been using Qlik the longest are likely familiar with the LEF method already, while the SLK may not be as widely known yet, which is why we frequently get questions around it.
In this blog post, we will cover the differences between the two activation methods, as well as what benefits the Signed License key brings to the table. Details on how to activate them will follow in the second post to this short series.
What is a Signed License Key (SLK)?
The SLK is an encrypted JSON web token used to activate Qlik Sense Enterprise or ABDI. It contains product information, available access types for users, and any applicable product add-ons or limitations.
An SLK is currently optional for Qlik Sense Enterprise on Windows and should not be used with license tokens.
You cannotchange from an SLK activated system to a LEF activated system.
The SLK requires online connectivity to our licensing server for both activation and continued operation.
Every license has a LEF. Each 16-digit license number that you get can be translated into a LEF, regardless of the method used to activate the license. The LEF itself contains all the instructions for the Qlik Product, such as license level, numbers of users, access types available for assignment, as well as all the limitations or add-on.
When applying your license using the license number and control number, the LEF will be downloaded to the product during activation. It will be updated with each refresh request.
The first line of the LEF is always your 16-digit license number and it ends with a checksum so that an unauthorized alteration of the content is impossible.
It requires a control number for activation
You can change from a LEF activated system to an SLK activated system (but not the other way around). Always use LEF activation if your license has tokens.
Your signed license key will be sent to you in the license delivery email.
If you did not receive your SLK via email, please contact Customer Support. Please make sure to provide the corresponding 16-digit license key and the Support team will be able to get the SLK for you.
There is no way to get the SLK from the Support Portal at this time.
Benefits of using an SLK
Using the Signed License Key makes more product and deployment options available to you.
Examples of these are:
Multi-site deployments, such as connecting a Qlik Sense Enterprise site with a QlikView Server deployment using Qlik Sense Enterprise license options. This is enabled by accepting a Dual-Use offer for each QlikView deployment that should be enabled for a Unified License scenario.
Multi-geo deployments, such as having Qlik Sense Enterprise sites in different locations using the same list of users.
Qlik Sense Enterprise for Kubernetes and Qlik Cloud Services. Either stand-alone or in a multi-cloud setup.
Consumption-based licenses, such as Qlik Sense Enterprise Analyzer Capacity. This additional user license is possible to use in a single or multi-cloud scenario.
All the above is enabled by the use of the Signed License Key. This is made possible by the local deployment syncing all entitlement data (assigned users access, etc.) with all available deployments sharing the same SLK. The synchronization is done using the Qlik Licensing Services and our license backend hosted in Qlik Cloud.
And this is it for an overview of our available license types and activation methods. We’ll follow this up with part two soon, detailing the move from a LEF activated license to an SLK. Until then, give this post a like if you found it helpful! And please let us know if you have any questions or feedback in the comments.