With a Unified license (formerly called Dual Use License) the legacy QlikView license is complemented with a Qlik Sense license that can be applied to the QlikView server as it includes QlikView entitlement license attributes. Such license needs to be activated with the Signed License Key (SLK). When a customer enters an Analytics Modernization Program (AMP, formerly known as Dual Use program), QlikView CALs (e.g. Named User CALs, Document CALS, Session CALs and Usage CALs) are converted into Professional User, Analyzer User,  and Analyzer Capacity User allocations based on the Analytics Modernization Program conversion ratios.

Here are two scenarios:

I. If a customer transitions to AMP with on-premise (client-managed) Qlik software (e.g. converts to the perpetual estate or convert to subscription Qlik Sense Enterprise on Windows), a Unified License containing the converted quantity of Professional Users, Analyzer Users and Analyzer Capacity would be delivered. This license contains a customized Qlik Sense Enterprise Signed License Key (SLK) which can also be deployed on QlikView Server and/or QlikView Publisher. If a user is assigned a Professional or Analyzer user license, this assignment information is synchronized to all Qlik Sense and QlikView deployments activated using this Unified License key. As such one user just needs one license to access the entire Qlik software platform (regardless if it is Qlik Sense or QlikView).

In this scenario, as long as the QlikView Server and Qlik Sense edition use the same Identity Provider (IdP) the user can access apps on both environments consuming only one user license allocation.

If the user license is reallocated in any of the systems to a different user, the same will occur across both QlikView and Qlik Sense environments.

II. If a customer transitions to AMP with Qlik Sense Enterprise SaaS add-on, a Qlik Sense Enterprise SaaS tenant may use a Unified License  for the on-premise deployment. The customer is able to upload QlikView document prepared by the on-premise QlikView software directly into Qlik Sense Enterprise SaaS for distribution.

A QlikView Server or a Qlik Publisher software can be activated in two ways:

1) Using a legacy method with 16-digit QlikView license key and the corresponding control number

2) Using a modern Unified License with Signed License Key containing needed QlikView Server and Publisher Service attribute(s). In this latter scenario, user license assignment (Professional/Analyzer) and analyzer capacity would be synchronized with other deployments using the same Signed License Key as it is done in the Unified License model

If the customer opts to remain in Perpetual licensing, the existing QlikView license model can be retained. Otherwise, if the customer opts for conversion into Subscription licensing model, a set of QlikView subscription license attributes mirroring the existing QlikView perpetual license key setup would be delivered such that the customer switch to the subscription QlikView keys without the need for an immediate migration project towards using Unified licensing.

Note: Please note that Qlik is no longer starting clients on the Perpetual license model. See End of Perpetual License Sales 

Environment:

• QlikView 
• Qlik Cloud 
• Qlik Sense Enterprise on Windows 
   

Related Content:

• How to Apply an unified Signed License Key for QlikView and Qlik Sense
• Qlik Multi-Cloud Frequently Asked Questions (FAQ)

Before you can start using Qlik Sense Desktop, you need to authenticate yourself against a Qlik Sense Enterprise server. You need to have a working network connection to enable authentication.

The following requirements need to be met:

• A functioning network connection to the Qlik Sense Enterprise Client-Managed Server or Enterprise SaaS/Business tenant.
• Use of a Professional license. Analyzer licenses do not support Desktop Authentication
  For legacy token license: User and Login Passes allow Desktop Authentication
• No TEST license. Test licenses disallow the use of authentication links 
• Compatibility must be met. See Qlik Sense Desktop patch process and compatibility with on-premise installs and Qlik Cloud .

After you have been authenticated once, internet access is not required to continue using Qlik Sense Desktop. However, you have to re-authenticate yourself if thirty days have passed since you last authenticated.

Environment

Qlik Sense Desktop 
Qlik Cloud 
Qlik Sense Enterprise on Windows 
Qlik Sense Business 

Related Content 

Starting Qlik Sense Desktop | Qlik Sense on Windows Help 
Starting Qlik Sense Desktop | Qlik Cloud Help
Configuring Qlik Sense Desktop authentication link 
How to authenticate Qlik Sense Desktop against SaaS editions 
How to authenticate Qlik Sense Desktop against a Qlik Sense Enterprise on Windows server  

The problem occurs when applying a valid SLK to QlikView. When clicking Apply License, the following error is shown:

Error when applying license: Post "https://license.qlikcloud.com/v1/definitions/signed": net/http: invalid header field value for "Authorization"

Resolution

This error occurs when the license code is copied with line break characters. Those are considered as part of the license, invalidating the code.

To resolve the problem, copy the license code in a text file editor and manually remove the line break characters. Then copy the correctly formatted string to activate the license. 

When removing the line breaks, verify that no other characters are deleted.

Example of an incorrectly and correctly formatted key:

Environment

• QlikView all versions

As License Token is only valid for 90 days after it was created, it is renewed automatically by Talend Administration Center, except if Talend Administration Center is not connected or cannot access Talend Token Site.

You will be experiencing a situation where the License Token will not automatically renew in Talend Administration Center.

Resolution

1. For Talend Administration Center License Token to automatically renew, you must have access to the Internet. Please check if you are getting any Internet connection issues during the time. 
2. Please check if you have any proxy settings that may block the connection to the license token validation server (https://www.talend.com/api/get_tis_validation_token_form.php) and please reference the following: Proxy and firewall allowlist information

   Port 443 is the port to access the license token validation server.

3. Please feel free to contact our Customer Support staffs in order to check the expiration date of your Talend Administration Center License Token from here: Support.
4. If you are using a patch before the TPS-5612, it would be advised to move to a patch TPS-5612 or later.
   • There has been a following fix for the "License Token will expire in x days" alert message in TPS-5612 patch. The alert message shows starting from 10 days before the License Token expiration date, and the License Token will try to automatically renew once everyday in the 10 days. However, if there are Internet connectivity issues during the time, the License will not successfully renew automatically.
     In order for the License Token to automatically renew, we have implemented a feature for the license to try to renew again upon failure everyday. (The license will try to renew check per day, once it failed and will do it again). Please see the following document for details: TPS-5612 (cumulative patch).
   • You can always check the technicalvariable table in the Talend Administration Center database. The value for the datetokencheck will be the date of Talend Administration Center License Token renew check( this date is On a weekly basis). The calculation of this value is: Year * 1000 + Month * 10 + Week of Month. For Month and Week of Month, it will start the count from 0. If it is January, it will be 0, and if it is December, it will be 11. If it is the first week, it will be 0 and if it is the 5th week, it will be 4.
     For example, if the value is 2025012 for the datetokencheck, it would mean the Year is 2025, the Month is February, and the Week of Month is the 3rd week. LicenseTokenCheckDate 
5. If you already owned a license that has been reactivated by Talend after renewal, you may have to validate it manually from the Talend Administration Center web application. : How to validate a license after renewal.

Cause 

There are two potential causes:

• Talend Administration Center has experienced a connectivity problem with the License Token server.
• The License Token has not yet expired.

Related Content

For more information about how to clear Talend Administration Center Cache, please refer to this official article:

How-to-clear-the-Talend-Administration-Center-TAC-cache

Environment

Talend Administration Center 

You are a prospective customer and are looking to purchase a Qlik Cloud subscription.

• See How to purchase Qlik Sense SaaS digital subscription.
• If you are looking to manage an active subscription, see Managing Your Subscription in My Qlik.

You are a prospective customer, having never purchased Qlik licenses before and are interested in learning more about Qlik products and making a purchase:

• Go to Qlik.com to browse our available offerings and engage in our Live Chat if you have questions.
• Or contact Sales directly.

You are an existing Customer, having previously purchased a license directly from Qlik and wish to purchase additional licenses or CALs:

• Please contact your Account Manager. If you are unsure who the Account Manager is for your company, contact Support using Live Chat.

You are an existing Customer and purchased your licenses through a third party (not directly from Qlik) and wish to purchase additional licenses or CALs:

• Please contact your Responsible Partner from which you previously purchased licenses. If you are unsure who your Responsible Partner is, contact Support using Live Chat.

• Timeline
• Standard run vs third-party run
• Standard runs
• Third-party runs
• Possible third-party runs
• Transition of existing entitlements
• Starting Jan 30th (introduction of third-party runs, current packaging still applies)
• Starting April 2nd (switch to new packaging)
• Packaging details
• FAQ

 

Timeline

The below timeline illustrates how the various stages of this packaging update will happen. In-between each stage should be sufficient time to analyze your usage and prepare for the enforcement.

• January 30th – Introduction of third-party runs
• April 2nd – New third-party packaging is available for purchase 
• May 1st – Enforcement
  • Third-party limits for seat-based licenses
  • Third-party overages for capacity licenses

Standard run vs third-party run

Standard runs

An automation run is considered a standard run if it only executes blocks from the following categories:

• All Qlik connectors (Qlik Cloud Services, Qlik Reporting, Qlik AutoML, Qlik …)
• Base blocks (excluding Call URL & Cloud Storage)
• Mail & Microsoft Outlook

Example:

 

Third-party runs

An automation run is considered a third-party run if it executes any blocks that are not in the standard connector categories.

As a rule of thumb, a standard run will execute one or more blocks from third-party connectors. Among others, third-party connectors are connectors like Slack, Amazon S3, Microsoft Excel, Call URL. A full overview of all automation connectors if available here.

Example:

Every run of this automation will execute the Send Message (Slack) block.
This will make every run a third-party run as the Slack connector is a third-party connector.
The “Contains third-party blocks” label indicates that the automation contains an active third-party block.

Possible third-party runs

For a run to be considered a third-party run, we only evaluate executed blocks. If the third-party blocks in the automation were not executed, the run will not count as a third-party run. A block not being executed could be caused by many factors like Condition blocks, Filter List blocks, deactivated third-party blocks, ...

This illustrates that an automation with a “Contains third-party blocks” label will not necessarily generate third-party runs on every run.

Example:

This automation will only execute the Send Message (Slack) block if the reload fails (from the Do Reload block). This means it will only generate third-party runs depending on the state of the Condition block.

Transition of existing entitlements

Starting Jan 30th (introduction of third-party runs, current packaging still applies)

1. Customers who are entitled to included runs will get these as third-party runs
2. Purchased runs will be converted to third-party runs
3. Renewals before the end of March will maintain the same included third-party runs until next renewal.

Starting April 2nd (switch to new packaging)

1. Every new purchase will be using the new packaging
2. Renewals will revert third-party runs to the edition included quantity of the new packaging + any purchase of third-party runs using the new packaging

Packaging details 

The below table provides an overview of the new packaging for automations that will come in effect on April 2, 2025. Please reach out to your account manager for quotes and pricing related questions. 

 

FAQ

1. Will max concurrency be shared across run types?
Yes, both run types will count towards the same max concurrency.

2. Will usage of Qlik APIs through the Call URL block or other generic connectors count towards third-party runs?
Yes, when these blocks and connectors are used to make API requests to Qlik APIs, they will still count towards third-party runs. If you are missing blocks or functionality in a Qlik connector, please create an improvement request on our Ideation portal or support an existing request.

3. Will the new packaging have an included amount of third-party runs?
Yes, the new packaging will continue to provide some third-party runs for most editions of Qlik Cloud. Details are available in the above section "Packaging details".

4. Why are some automations with third-party blocks missing the label "Contains third-party blocks"?
An automation will only receive the label when someone performs a manual run or saves it in the editor. We are planning a new update that will apply this label to all automations with active third-party blocks regardless of someone saving them or not.
Please note that regardless of this label being on an automation or not, automation runs will still be evaluated and receive a correct billable yes/no label.

As a benefit of our Analytics Modernisation Program (AMP), a signed license key is issued as a unified license key. This enables the use of one license across Qlik Sense Enterprise on Windows and QlikView, granted the license has the required QlikView infrastructure attributes (QV_NODES for QVS, QDS_NODES for Publisher).

This allows for analyzer capacity to be shared across all systems using the same license.

Environment

QlikView 
Qlik Sense Enterprise on Windows 
With a Signed License Key (SLK) applied as a unified license across multiple environments 

Here is an example:

A QlikView server currently shows 18 minutes of consumption in the QlikView Management Console (Fig 1.) 

This can be accessed through: System (A) > Licenses (B) > Choose the License (C) > Professional and Analyzer access (D)

Fig 1

If a user accesses and consumes on a linked Qlik Sense Enterprise Server, the Qlik Sense Enterprise Management Console will show the up-to-date consumption. See Fig 2. Note the 24 minutes, an increase from the 18 we have seen in QlikView.

This can be accessed in the Qlik Sense Management Console > License Management > License usage summary

Fig 2

The usage on the server will be synchronized and shown on the other linked servers within approximately 10 minutes. See Fig 3 and note the 24 minutes, which matches the value in Qlik Sense.

Fig 3

For local consumption data, each server will store its own consumption and user information.   

For Qlik Sense Enterprise on Windows, the License Monitor app will show capacity consumption.

For the QlikView Server, the capacity consumption is shown and stored in the local session log file, with the CAL consumed being Analyzer Capacity, with a log entry like this:

RLS64 12.50.20200.0 20210412T132942.000+0200 20210412T133617.000+0200 C:/ProgramData/QlikTech/Documents/retail store performance.qvw 20190220T113522.000+0200 Socket closed by client 20210412T133601.000+0200 00:00:16 0.000000 10228 1303493 31 2 QTSEL\ghd 1718e2e6-5b1c-4b9e-87a9-d9200f55e37a Ajax QvWS 12.50.20200.0 browser.msie illa/5.0 (windows nt 10.0 On 4747 fe80::df3:cd38:b86f:50bd 58495 Analyzer Capacity 6 315dcfab-7448-4f4b-8209-ef34742b1abe

Long term offline capability for the releases April 2020 and onwards requires a change to the license (addition of a further attribute) which can only be added after a special approval from the Customer Success Organization.

See below on how to hand in the request for approval and how to proceed. 

1. Contact Qlik Support team via Chat or via Qlik Support Portal.
2. You will need to sign an offline addendum and share the signed addendum with Qlik Support, there are 2 addendums one for banking and one for non banking customers. You can find the addendum attached in this article.
3. Provide the License key as well as the current Product version details and the reason why the connection to Qlik's license back end (LBE) cannot be established.
4. Once the license is processed and fulfilled, here is how the license activation process for the long term offline is done:
   1.  Long term offline use for Qlik Sense and QlikView Signed Licenses
   2. Long term offline use for Qlik NPrinting Signed Licenses
   3. Long term offline use for Qlik Catalog
5. As part of the agreement of granting a customer offline license usage, the customer is required to regularly upload User Assignment log files. See Offline User Assignment logs.

Related Content 

Activate Qlik Products without Internet access - April 2020 and onwards
Long term offline use for Qlik Sense Signed Licenses
How to send User Assignment log files to Qlik? (Long term offline license activation) 

Activating a Qlik GeoAnalytics license using the license tool may display the following warning:

The type initializer for 'Qlik.Sense.Lef.LefParser' threw an exception.

Only LEF licenses are affected. Signed key license keys will apply without a warning.

Resolution

This warning does not affect any functionality. It refers to an additional check failing, but still applies the license as expected. The warning can be safely ignored. 

Cause

The defect QB-29901 is, as of the writing of this article, still under investigation. 

Internal Investigation ID(s)

QB-29901

Environment

• Qlik Geo Analytics

This document explains the differences between Talend License Levels, and describes important steps that must be completed before lowering your license level with Talend products. Talend offers three different license levels: listed from advanced to basic, they are Master Data Management, Data Management, and Data Integration/ESB. Talend projects, Jobs, and components are not compatible across each of the licenses available, so if you lower a license without first performing the proper steps, the potential for critical problems is high. This document will help you successfully lower your license level with Talend products.

This article is relating to downgrading Talend Data Fabric license to Talend Real-Time Big Data Platform. The difference between the licenses is that the MDM features/user type is removed for RTBDP licenses. If you have a Talend Data Fabric license with any MDM projects, you'll need to proceed with the following steps below.

Understanding the three licenses and how they are layered

Licenses

The license used in Talend Administration Center enables an administrator to create and administer projects and users of different types. You can see what licenses you have available in Talend Administration Center by navigating to the Menu tree > Settings > Licenses.

The table below describes what you can do in your product according to your user type and license

Preparation & Migration

The example used here will be downgrading from Master Data Management to Data Management. If you are downgrading from Master Data Management or Data Management to Data Integration/ESB, the concept will be the same

Projects

You must create new projects inside of Talend Administration Center with the project type of Data Management, or to the level of the license you are downgrading to. To complete this part, you must log into TAC and locate Projects under the Menu tree. Since you are not able to change the project type on an existing project, you may duplicate a project, then select the correct project type. If you are connecting to GIT, verify that the settings and URL are correct under the Advanced Settings after duplicating or creating a new project.


 

Authorization

After the new project with the correct license level is created, you will not be able to see the project available in Studio until you provide the users with permissions. Inside of TAC, you will need to locate Project Authorizations under the Menu tree. Here you must choose the new project and provide the users with the desired permissions on the right side. In the Rights column, you can choose to give either Read Only or Read/Write by choosing the icon with the person and pencil. If you have any groups, you will need to choose the tab at the top center Authorization by User/Group to make sure the groups also have the proper permissions.


 

Users

Log into Talend Administration Center, navigate to the Menu tree, and locate Users. You must lower the users from MDM to DM (or the desired license level) on the right-side panel of each user that is selected. If applicable, you should verify that their GIT user is correct.

During this process, you should keep one user at your current license level until the end of the downgrading project, preferably the admin user.

If you are unable to change the user type, you may not have the proper permissions or the user may still be logged in.

To verify if the user is logged in, check the Users page of Talend Administration Center. You can see which users are logged into the Talend Studio, Talend Data Preparation, and Talend Administration Center. Log them out if needed.

Data Preparation and Talend Data Stewardship will not be covered in depth, but if the user is a Data Preparation or TDS user be sure to check the Data Preparation User box and select their desired roles.

Migration

To begin this portion, log in as the user at your current license level, as discussed in the Users section.

When you start up your Studio, be sure to choose the existing projects that have your current license level. If you are doing remote, you can verify the user that you are logging in with, so you know you are entering the correct projects and have proper permissions.



Once you have logged in to your current project, you will need to begin exporting your Jobs into a specified location.

To export a Job:

1. Right-click the Job, and select Export Job.
2. To the right of Select archive file, click Browse to choose the destination and name for the Job ZIP archive.
3. Select the Job Version.
4. Check the box to Export Dependencies.
5. Check all Options.
6. Click Finish.

You will then want to log into the new project, which should be empty and have the license level you will be downgrading to. Once you have logged in to that project, you will need to import the jobs you previously exported.


To import a Job:

1. Right-click Job Designs in the Repository, then select the Import items option.
2. In the next window, browse to a root directory or an archive file path where your exported items are stored. A list of items appears in the table.
3. Select the items you want to import. Choose the Overwrite existing items option if the items already exist in your repository and you want to overwrite them.
4. Click Finish.
5. If the newly-imported items do not appear, click Refresh to refresh the Repository.

Components

Once you have imported your Jobs, you will want to test them in the new project and verify that the components work and are not a part of the higher-level license that you plan to downgrade from. To confirm that your components function properly, review the Component Reference Guide

If you have any schedules, it would be a best practice to verify the Jobs run on the schedulers and any other unique designs you may have implemented.

Once you have verified that your Jobs run successfully on the new license platform, request the downgraded license from your Customer Success Manager.

Environment

Talend Administration Center 

Talend Studio 

Qlik NPrinting SLK License cannot be applied or updated after the upgrade.

Licensing fails with:

The Licence Service is not responding. Restart the Qlik NPrinting License service

The Qlik NPrinting log files read:

"errorMessage":"Post \"https://license.qlikcloud.com/v1/definitions/signed\": dial tcp: lookup license.qlikcloud.com: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.","errorType":"LICENSES-InternalServerError","level":"info","logTraceId":"bf71fd0bcf272dd3528824ac4fb5f3a6","statusCode":500

"error":"Post \"https://license.qlikcloud.com/v1/definitions/signed\": context canceled","level":"error","logTraceId":"d7c48ffd76242e3522db613652462ee5","message":"Failed to fetch license definition."

"errorMessage":"Too much time has passed since the last license update","errorType":"LICENSES-OutdatedLicense","level":"info","logTraceId":"e7c3a2cc454f5dc843b68e5bb5e6840c","statusCode":403

Resolution

This issue is being caused by the license server being unreachable. If the server has internet connectivity, then the likely root cause is a proxy being deployed.

Follow these steps to troubleshoot and resolve the issue:

1. Login to Qlik NPrinting Server with  Service Account and open Qlik NPrinting Web Console with NPrinting Service Account.
   
   
2. Verify that the Qlik NPrinting License service is up and running.
   
   
3. Try to restart the Qlik NPrinting License service and try to apply for the Qlik NPrinting SLK License before going to the next step.
   
   
4. Verify that the Qlik NPrinting server has an active internet connection and that connectivity to license.qlikcloud.com on port 443 is possible from the server running the Qlik NPrinting licensing service.  (You must get "default backend - 404" in the browser when accessed to license.qlikcloud.com)
   
   
5. In some rare cases, the Server only has temporary access to the Internet, so sometimes it is able to connect to https://license.qlikcloud.com and sometimes not. It needs to have permanent access to the licence-URL, to be able to correctly work.
   
   If you are in the above rare cases or if the sync doesn't seem to be performed, there is a way to force the sync: remove one/more characters from the SLK License and click to "apply".
   
   The license will be refused as it's an incorrect one. This action will force the license synchronization. Now, try to apply with an actual SLK License.
   
   
6. If the above did not resolve the issue, check if you have a proxy configured in the NPrinting Server.
   
   
   1. Open Internet Options from Control Panel and check for Proxy IP/URL
      
      
      
      
   2. If the Proxy is configured, do the changes accordingly in %Program Files%\NPrintingServer\NPrinting\License\license.configusing Licensing service proxy Setup 
      
      
   3. Make sure to Stop and Start the Qlik NPrinting licensing service before and after performing the changes.

Cause

When you upgrade the Qlik Nprinting Server, the existing configurations files will be overwritten to default configurations files, and any changes done before the upgrade have to be updated again.

So make sure to take a backup of the Files (Eg: Config) and Folders before performing the upgrade.

Environment

Qlik NPrinting 

Related Content

Licensing service proxy authentication 
Licensing Qlik NPrinting offline 

Question I

What is the expiration period for a license token?

90 days. This is not guaranteed though and it may differ among customers.
Also, the 90 days may change in the future, so please check with a license specialist if not certain.

Question II

Can the license validate automatically after renewal?

In the reference below, it mentions that “you may have to validate it manually from the Talend Administration Center web application.". There is a chance that it may not validate automatically, and if that is the case, they would have to manually validate their license.

For more information about How to validate a license after renewal, please refer to Qlik Talend Documentation: validate-license-after-renewal 

Question III

What is the URL/port to open to access the Internet and validate the license from TAC?

The URL is not required. The port is 443.

Question Ⅳ

What is the validation token form URL?

You will get the validation token form here:

https://www.talend.com/api/get_tis_validation_token_form.php

Environment

Talend Studio 

Talend Administration Center 

Talend Cloud 

Content

• Background
• Qlik Licensing Service (QLS)
• Signed License Key (JWT)
• What is a JSON Web Token?
• What’s in this for me as a Customer?
• Activation Using the Signed License Key
• Frequency in which license information is updated
• Data Transmitted by an Activation Request
• Activation Reply
• Analyzer Capacity License Report Process
• Data Transmitted
• Sync Reply
• User Assignment Sync Process
• Data Transmitted
• Reply fromLicense Backend

Background

Qlik Products have generally utilized license keys to enforce license entitlements and use rights.  During activation, the licensed entitlement is downloaded to the product in the format of a Licensing Enabler File (LEF). Activation requires internet connectivity to the deployment and is triggered by entering a 16-digit serial number and a corresponding control number. Offline activation is also supported using a manual LEF by copying and pasting a text file into the activation user dialog. Communication is through an http protocol.

Qlik Licensing Service (QLS)

Introduced with the February 2019 release[GM1]  of Qlik Sense Enterprise, Qlik has developed an alternative process for product activation. There have been several drivers for this change, including a move to an https protocol for a more secure connection between the Customer deployment and Qlik infrastructure. More information follows below. 
 
To allow for Customers to make the decision when to move, Qlik has introduced the use of a Signed License Key to determine which activation method to use. Over time Qlik Licensing Service will replace the current activation process, but for now both methods of activations will work.

Signed License Key (JWT)

As mentioned above, Qlik has added one additional way to activate Qlik products. 

What is a JSON Web Token?

JSON Web Token (JWT) is an open standard (RFC 7519) that defines a compact and self-contained way for securely transmitting information between parties as a JSON object. This information can be verified and trusted because it is digitally signed. JWT’s can be signed using a secret (with the HMAC algorithm) or a public/private key pair using RSA or ECDSA.
 
Although JWT’s can be encrypted to also provide secrecy between parties, we will focus on signed tokens. Signed tokens can verify the integrity of the claims contained within it, while encrypted tokens hide those claims from other parties. When tokens are signed using public/private key pairs, the signature also certifies that only the party holding the private key is the one that signed it. That is why we refer to this as the Signed License Key.

What’s in this for me as a Customer?

With the use of a Signed License Key, there are more Product and deployment offers to use.

• Use of 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.
• Use of multi-geo deployments, such as having Qlik Sense Enterprise sites in different locations using the same list of users.
• Use of the consumption-based license, Qlik Sense Enterprise Analyzer Capacity. This additional user license is possible to use in a single or multi-cloud scenario.

All of the above is enabled by the use of the Signed License Key. This made possible as the local deployment will sync entitlement data with all deployment’s using the same Signed License Key through an online database, License Backend, hosted by Qlik within Qlik Cloud.

Activation Using the Signed License Key

This is initiated by entering a Signed License Key to the Control Panel. The request is performed by the service Licenses using port 443 (https protocol procedures applies).

Frequency in which license information is updated

Assignment information (what user has what type of access assigned) is synchronized from the license service to license.qlikcloud.com every 10 minutes. 
Changes to a license (such as adding additional analyzer capacity) can take up to 24 hours to be retrieved.

Data Transmitted by an Activation Request

Activation Reply

Analyzer Capacity License Report Process

(Time schedule is not disclosed and includes grace time to support outages in the internet connection, a/k/a Optimistic Delegation.)

Data Transmitted

Sync Reply

User Assignment Sync Process

Data Transmitted

Reply from License Backend 

 
This Reference Guide is intended solely for general informational purposes and its contents do not form part of the product documentation.  The information in this guide is subject to change without notice.  ALL INFORMATION IN THIS GUIDE IS BELIEVED TO BE ACCURATE BUT IS PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED.  Qlik makes no commitment to deliver any future functionality and purchasing decisions should not be based upon any future expectation.

Analyzer Capacity Licenses can be assigned automatically based on Analyzer Capacity License Rules. These rules can be set up to provide Analyzer Capacity to users, groups, or anonymous users.

This article covers what function the license type has, how to assign it, and how to track usage. 

Index:

• What is an Analyzer Capacity license?
• How to assign Analyzer Capacity Licenses
• Assigning Analyzer Capacity in Qlik Sense Enterprise SaaS:
• Create an Analyzer Capacity License Rule in Qlik Sense Client-Managed:
• How to monitor Analyzer Capacity usage
• Qlik Cloud
• Qlik Sense Enterprise on Windows Client Managed
• In QlikView
• How Qlik Sense Analyzer Capacity Works (video)
• Related Content
• Environment

What is an Analyzer Capacity license?

The Qlik Sense Analyzer Capacity license type is automatically assigned to users not assigned a Professional or Analyzer license and consumes time during an active session with the minimum session length set to 6 minutes.

Overview:

• An Analyzer Capacity license type would typically be used by users not assigned to any of the available named user types (Professional or Analyzer).
• The capabilities for the Analyzer Capacity license type are similar to the current Analyzer user type and supports the same features. 
• Analyzer Capacity is available for:
  • Qlik Cloud 
  • Qlik Sense Enterprise on Windows
  • QlikView.
• Analyzer Capacity works with Both Signed License Key and Signed License Definition.

Details:

• The minutes are based on a monthly subscription, which resets at 0:00 UTC time on the first day of the calendar month.
• Consumption is in 6-minute blocks. No consumption during idleness.
• Overage can be added to the subscription. See How to manage Overage for Analyzer Capacity.

How to assign Analyzer Capacity Licenses

Assigning Analyzer Capacity in Qlik Sense Enterprise SaaS:

No setup is required. If no Professional or Analyzer License was assigned, Analyzer Capacity is automatically allocated. 

See Enabling dynamic license assignment for details. 

Create an Analyzer Capacity License Rule in Qlik Sense Client-Managed:

1. Open the Qlik Sense Management Console
2. Go to Licenses Management
3. Open Analyzer Capacity Rules in the right-hand menu (See fig 1)
4. Click Create new 
   
   Fig 1
   
   
5. Provide details for your rule. In our example, we are enabling users in the group capacity to receive Analyzer Capacity Licenses. 
   
   Name: Name of your rule
   Description: Description of your rule
   Actions: Allow access 
   
   Populate the conditions accordingly. See Fig 2.
   
   Fig 2
   
   If you are looking to provide access for anonymous users, see How to allow Anonymous Hub access in Qlik Sense Enterprise on Windows.
   
   
6. Click Apply
7. All users in the defined group will now receive an Analyzer Capacity License. 
   
   
   

How to monitor Analyzer Capacity usage

Qlik Cloud

The Entitlement Analyzer for Qlik Cloud provides detailed usage data for Analyzer Capacity, but a tenant admin can gain an overview through the Management Console at any time:

1. Open the Qlik Cloud Management Console
2. Open the User allocation tab
3. Open the Overview tab
4. Review the current Analyzer capacity usage 
   
   
   
   

The Entitlement Analyzer is only available for Qlik Cloud.

Qlik Sense Enterprise on Windows Client Managed

The bundled License Monitoring app provides usage data for Analyzer Capacity, but an administrator can gain an overview through the Qlik Sense Management Console at any time:

1. Open the Qlik Sense Enterprise on Windows Management Console
2. Go to License Management
3. The License usage summary tab (a) lists the current Analyzer capacity usage (b)
   
   
   
   

In QlikView

1. Open the QlikView Management Console and go to System
2. Open the Licenses tab
3. Select License 
4. Switch to the Professional and Analyzer access tab.
5. The General tab lists the current Analyzer Capacity usage 
   
   

How Qlik Sense Analyzer Capacity Works (video)

Related Content

Analyzer capacity license and monitoring (Client Managed)
Qlik Licensing Service Reference Guide 
Assigning user allocation (Qlik Cloud)
Analyzer capacity license (Qlik Cloud)
Top 5 things to know about modern Qlik Licensing

Environment

QlikView 
Qlik Sense Enterprise on Windows 
Qlik Cloud 

Introduction

As a Talend Test Migration License is generated for a period of 60 days (2 months) at a time, how to extend your Talend Test Migration License when it is expiring or already expired in Talend Studio/Talend Administration Center?

Resolution

Please create a new case in Qlik Customer Support Portal so that our Support can generate a new test migration license for you. As long as there is a current subscription of the account, a test migration license will be provided.

Please keep in mind that a Talend Test Migration License is valid for 60 days(2 months) a time.

If you are looking to obtain a Test Migration license, see How to Request and Utilize a Talend Test Migration License.

If you are looking for Qlik Support Case Portal, see How to contact Qlik Support 

Environments

Talend Studio 

Talend Administration Center 

When purchased, our Qlik products are delivered with a 16-digit license key (LEF) and/or the Signed License key (SLK). What key is applied may differ depending on your requirements or the version of the product.

You’ll have two activation options:

• The Signed License key (SLK), available for most Qlik products
• (legacy) And a combination of the 16-digit key, a control number, and the License Enabler File (LEF)

These license activation methods cannot be mixed. A license activated with an SLK cannot also be activated using the key + control number method.

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.
• The SLK is to be used for activating Qlik Sense Enterprise on Windows licenses using the Professional/Analyzer user model. Qlik Sense Core Based and Token based licenses should use the legacy LEF activation method.
• You cannot change 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.
• For information on how to apply an SLK, see How to Apply a Signed License Key
• The time (Subscription date, Analyzer capacity reset) is on UTC

The SLK is mandatory for:

• The use of Qlik Sense Analyzer Capacity licenses
• Any deployments using Qlik Sense Enterprise on Kubernetes or Qlik Sense Enterprise on Cloud Services, as well as Multi-Cloud (a combination of Qlik Sense Enterprise on Windows and Cloud offerings)
• Unified Licenses, which combine Qlik Sense and QlikView
• See Qlik product licenses for more information.

What is a License Enabler File (LEF)?

• 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.
• The LEF can be activated offline and used offline, see How to license a QlikView or Qlik Sense server without Internet access for details.
• The time (Subscription date) is on UTC

The LEF activation method is currently required for:

• Qlik Sense
  • Core-based licenses
  • Token-based licenses
  • See Qlik product licenses for more information.
• QlikView
  • CAL-based licenses
  • See Licensing QlikView for more information. 

How do I get an SLK?

• 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.

If you are curious about more information around the Qlik Licensing Service, see the Qlik Licensing Service Reference Guide.

How do I get a LEF?

• You can get the LEF and control number from the Support Portal by following the steps outlined in How to request a control number and LEF

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.