If a TCP connection is possible with Qlik's licensing server endpoint, testing the connection to license.qlikcloud.com will return the message default backend - 404.

When testing whether or not your Sense installation can successfully connect to the license backend, always test the connection with all nodes.

1. Open any web browser
2. Navigate to  https://license.qlikcloud.com
3. The response should be default backend - 404.
   
   Other results, such as Can't reach this page or This site can't be reached with the error code ERR_CONNECTION_TIMED_OUT, indicate the Qlik Sense server cannot establish the needed TCP connection to the license server on the internet.

The 404 HTTP error code indicates the server was reached but could not find any content to be displayed in the URL address specified.

Another test would be to use telnet (which needs to be installed on the server) to confirm a connection to port 443 is possible:

1. Open cmd as an Administrator
2. Type telnet license.qlikcloud.com 443, and hit Enter.
3. Confirm a blinking cursor is returned, which indicates a TCP-level connection has been established

If different results are returned:

• verify that the connection to license.qlikcloud.com:443 is allowed in your environment, such as by verifying firewall settings or other network security deployments
• if a web proxy is required for internet access, see Configuring a proxy for Qlik License Service communication in Qlik Sense Enterprise on Windows 
  
  

Environment

• Qlik Sense Enterprise on Windows, all versions licensed with a Signed License Key (SLK)

Related Content:

There was an error when getting license information from the license server  

This article provides an overview of how to manage users using Qlik Application Automation. This approach can be useful when migrating from QlikView, or Qlik Sense Client Managed, to Qlik Sense Cloud when security concerns prevent the usage of Qlik-CLI and PowerShell scripting.

You will find an automation attached to this article that works with the Microsoft Excel connector. More information on importing automation can be found here.

Content

• Prerequisites
• Sheet Configuration
• Automation Configuration
• Running the Automation
• Considerations
• Related Content

Prerequisites

• Access to a Qlik Cloud tenant
• User assigned the role of Tenant Admin
• Office 365 account (for Microsoft Excel)

Sheet Configuration

In this example, we use a Microsoft Excel file as a source file to manage users. A sheet name, for example, Users, must be added and this must also be provided as input when running the automation. The sheet must also contain these headers: userId, Name, Subject, Email, Roles, Licence, and Flag.

Example of sheet configuration:

If users are to be created the Flag column must be set to create. If users are to be deleted, there's no need to include roles, but Flag must be set to delete.

Automation Configuration

1. Add an Input block that takes the name of the worksheet from which data should be read as input. You also need to specify the first and last cell to read data from, as well as if users are to be created or deleted.
   
   
   
   
2. Add two variables of the type number. One to keep track of created users and one to keep track of deleted users. These variables will be used to update the run title when the automation has been completed. Only one of them will be used when running the automation since only one of the modes can be used (Create or Delete). Let's call the variables UsersCreatedCounter and UsersDeletedCounter.Intially set these variables to 0.
   
   
3. Add the Get Current Tenant Id block from Qlik Cloud Services Connector.
   
   

4. Add the List Rows With Headers block from the Microsoft Excel connector to read the values that have been configured in the Excel sheet. 

   • Use the "do lookup" function to find the Drive ID and Item ID of the file you will be using as a source. 
   • Configure the other fields to get the values from the input fields. 
     
     
     
     
5. Inside of the List Rows With Headers loop add the Search Users block from the Qlik Cloud Services connector. Configure Fields and Filter input parameters as shown below.
   
   
   
   
6. Add a Condition block to check if the user exists, if we're in Create mode, and if the Flag column in the Excel file is set to create.
   
   
   
   
   
7. If the conditions are true,  add the below variables by initially setting all these variables to empty:
   
   
   1. Roles: List variable to store a list of roles that needs to be assigned to the user. Configure the variable by clicking on Add operation button and selecting the 'Merge other list into Roles' option. In the List field, use explode formula to convert comma-separated roles from the Role column in the Excel file into a list.
      
      
      
   2. AssignedRoles: Variable of type object to store the role ID as key-value pair.
   3. AssignedRolesList: List variable to store the AssignedRoles object variable as an item.
      
      
8. Add a Loop block to loop through the Roles list variable where the roles of the user are stored from the Excel file.
   
   
   
9. Add the List Roles block from the Qlik Cloud Services connector to retrieve the IDs of the roles. Configure the Filter input parameter as shown below.
   
   
   
10. Add AssignedRoles object variable to store role ID. Configure the variable by clicking on Add operation button and selecting the 'Set key/values of the AssignedRoles' option. Click on Add key/value button and use the ID as the key and the ID from the output of the List Roles block as the value.
    
    
    
    
11. Add the AssignedRolesList variable to store the AssignedRoles object variable as an item to this list variable. To do this click on Add operation button and select the 'Add item to AssignedRolesList' option. In the Item field map the AssignedRoles object variable.
    
    
    
    
12. Add the Raw API Request block from the Qlik Cloud Services connector to create the user. Configure the block as shown below.
    
    
    
    
13. Add the Condition block to check if the user has been created. If the condition is true increment the UsersCreatedCounter variable by 1.
    
    
    
    
    
    
14. Add the Condition block to check if we need to allocate a license to the user created in the above step.
    
    
    
    
15. If the conditions are true, add the Raw API Request block to allocate a license to the user. Configure the input parameters as shown below.
    
    
    
    
16. If the first condition in the List Rows With Headers loop is false, then use another Condition block to find out if we are in Delete mode, if the flag column in the Excel file is set to delete, and if the user exists.
    
    
    
    
17. If the conditions are true, add another Condition block to check if the user has a named license.
    
    
    
    
    1. If the condition outcome evaluates to true, add the Raw API Request block to deallocate the user's license. Configure the input parameters as shown below.
       
       
       
       
       
18. Add the Raw API Request block to delete the user. Configure the input parameters as shown below.
    
    
    
    
19. Add the UsersDeletedCounter variable and increment it by 1.
    
    
20. The last part of this automation is to check the mode and update the automation's run title to display how many users have been created or deleted.
    
    
    
    
    
    

Running the Automation

When running the automation you must provide input to the automation, this includes the name of the worksheet to read data from. You also need to specify the first and last cell to read data from, as well as if users are to be created or deleted. Example :

Considerations

• A multitenant scenario can be supported by utilizing the Qlik Platform Operations connector instead of the Qlik Cloud Services connector. 
• Google Sheets could be used instead of Microsoft Excel.

The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.

Related Content

How to manage space membership (users)

Environment

• Qlik Cloud 
• Qlik Application Automation

This article supplements documentation that requires changes to the Qlik Sense Engine Settings.ini. No settings are provided in this article. 

Steps:

1. Stop the Qlik Sense Engine and Qlik Sense Service Dispatcher services on all nodes with engines.
2. For each of the nodes: open Notepad as Administrator
3. Open the Settings.ini file. Default location: C:\ProgramData\Qlik\Sense\Engine\Settings.ini
4. Modify the file to fit this schema:
   

   [Settings 7]
   Key=Value
   

   
   Note the blank line at the end of the file.
   
   The file will look like this:
   
   
   
   
5. The key and value will be provided by other knowledge articles or by a Qlik Support technical resource
6. Save the file
7. After these changes have been made on all nodes, start the Qlik Sense Engine and Qlik Sense Service Dispatcher services on each node.

If you are looking to modify the Qlik Sense Desktop client settings.ini:

• The file is found in:  C:\Users\<username>\Documents\Qlik\Sense\Settings.ini 
  Where <username> will be the user who installed Qlik Sense Desktop.
• The steps remain the same, although no services need to be restarted.

This article explains how the Qlik Reporting connector in Qlik Application Automation can be used to generate a bursted report that delivers recipient-specific data.

For more information on the Qlik Reporting connector, see this Reporting tutorial.

This article offers two examples where the recipient list and field for reduction are captured in an XLS file or a straight table in an app. Qlik Application Automation allows you to connect to a variety of data sources, including databases, cloud storage locations, and more. This allows you to store your recipient lists in the appropriate location and apply the concepts found in the examples below to create your reporting automation. By configuring the Start block's run mode, the reporting automations can be scheduled or driven from other business processes.

Contents

• Using a straight table as a distribution list
• Using an Excel File as a distribution list

Using a straight table as a distribution list

In this example, the email addresses of the recipients are stored in a straight table. Add a private sheet to your app and add a straight table to it. This table should contain the recipients' email address, name, and a value to reduce the app on. We won't go over the step-by-step creation of this automation since it's available as a template in the template picker under the name "Send a burst report to email recipients from a straight table".

Instead, a few key blocks of this template are discussed below.

1. List Values Of Field. This block will return a list of all values of the specified field. The selected field should directly map to the recipient scope of data to be delivered. For each value, a report will be generated and distributed to the recipients who have that value assigned in the distribution list. We'll call this value the scope of the report, an example field could be Region to build a report for each different region and delivery to regional employees.
   
   
2. The Create Report block and attached blocks will then be executed for each unique value of the field. Tip: you can dynamically name your reports by mapping the current field's value to the Report name parameter of the Create Report block:
   
   
   
   
3. Add any sheets to the report by using the Add Sheet to Report block. Use the block Add Selection To Sheet to add selections. Add at least a selection for the current scope of the report. Also, apply a selection to the app using the Select Field Value block. This will reduce the straight table that contains the distribution list to the current scope.
   
   
4. Now, use the block Get Straight Table Data and configure it to retrieve the distribution list. The important step here is to append each email address from the distribution list to a string variable. Also, add a semicolon ';' to the field to separate the email addresses. 
   
   
   
   
5. The scope from the distribution list should be used to add a sheet to the report and apply a selection for the current recipient. For example, if the recipients are sales reps, this could be used to provide an overview of each recipient's individual sales.
   
   
   
   
6. Use the Generate Report block to finalize the report. Map this block's output to the attachment parameter of the Send Mail block. Map the string of email addresses to the To input field of the Send Mail block.
   
   
   
   
7. Then make sure to execute the block Unlock Selections to allow the selections to be overwritten for the next report scope. Also, empty the email addresses from the string variable to make sure they aren't persisted for the next scope.
   
   

Helpful tips

1. The Output block can be used to keep track of the automation's progress by showing the current scope.
2. When building the report automation, you can test the email output by sending the report to yourself before using the distribution variable for operational execution.
3. It's also possible to use the Copy File block from the Cloud Storage connector to store a copy of the report on any file storage system like Dropbox or SFTP. 

Using an Excel File as a distribution list

In this example, the email addresses of the recipients are stored in an Excel file. This can be a simple file that contains one worksheet with headers on the first row (name, email & a value for reduction) and one record on each subsequent row. 

1. The first step is to gather the Excel file's item id. This can be retrieved from the URL when the file is open in a browser window or by executing the List Items In Root Folder Of Drive block. Execute this block in a test run to fetch these records.
   
   
   
   
2. The results from the test run can now be used in other blocks, click the Item Id input field of the List Rows WIth Headers block and select the id key from the right item in the output returned by the List Items In Root Folder Of Drive block. 
   
   
   
   
3.  Further configure the  List Rows With Header block by specifying the worksheet name and the dimensions of the data (header row included). Below is an example of the excel file shown at the beginning of this section.
   
   
   
   
4. The other steps of the automation are similar to the first part of this article so they won't be repeated here. Optionally, values from the Excel file can be used for reducing the report with the block Add Selection To Report. 
   
   

The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.

Qlik can technically provides a license that is stored in the TDC database server, which supports more than two TDC servers. However, it is important to remember that your sysadmin/devops must be very careful from the deployment perspective as they must develop scripts to ensure the following:

• Only one TDC server can be active at a time, with the other TDC servers in a passive or down state.
• When switching from passive to active, the TDC database server must be accessible (either shared or replicated) to the other TDC servers.
• It's essential to consider the TDC data, particularly when accessing the search index. For the new version 11.1 (TDC 8.1), it might be advisable to utilize an external Solr server/service that's accessible to the all servers.

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 

Qlik Replicate tasks using Oracle as a Source Endpoint fail after installing the Oracle July 2024 patch. 

All Qlik Replicate versions older than the 2024.5 SP03 release are affected.

Environment

• Qlik Replicate 2024.5 SP02 and below
• Oracle Source Endpoint with Oracle 2024 July patch (version 19.24)

Resolution

Upgrade to Qlik Replicate 2024.5 SP03 or later once available. 

In the meantime, Qlik has made early builds of 2023.11 and 2024.5 available. 

Download the early builds here: 

2023.11 SP05: https://files.qlik.com/url/ndafzunah2srntqt
password: bl3xrefv

2024.5 SP03: https://files.qlik.com/url/fbfsznjidxt5nzra
password: cygie73l

Cause

The Oracle July 2024 patch introduced a change to redo events. Qlik has since provided a fix for Qlik Replicate which parses the redo log correctly. 

Internal Investigation ID(s)

RECOB-8698

Reference:

Oracle Database 19c Release Update July 2024 Known Issues

As a general reminder, all changes to the environment such as operating system patches, endpoint and driver patches, etc. should be tested in lower environments before promoting to production.

Using Open in Server in QlikView Desktop to connect to a QlikView server fails with: 

Connected to server OK, No reply received
Switching to HTTPS tunnelling
Connected to server OK, Security settings denies access
Switching to HTTP tunnelling
Connected to server OK, No reply received

The Desktop client is running version May 2023 (12.80) or later, while the QlikView server is a previous version, such as May 2022 (12.70).  

Resolution

If QlikView Desktop and QlikView Server are running different versions, either upgrade the lower version to match the higher version or set the correct and same session algorithm in the Settings.ini file to resolve the discrepancy.

For issues where the QlikView Desktop is running version May 2023 (12.80) and the QlikView Server is running version May 2022 (12.70) or earlier, the QlikView Desktop settings.ini file must contain the entry SessionAlgorithm=CALG_AES_128.

Modify the QlikView desktop client settings.ini to add SessionAlgorithm=CALG_AES_128. For information on how to modify the settings.ini, see: How to change the settings.ini in QlikView Desktop and QlikView. 

Cause

The discrepancy in the session algorithm causes the error. QlikView May 2023 (12.80) now uses AES256 encryption instead of AES128, which was used in QlikView May 2022 (12.70) and earlier. 

Related Content 

What's New in QlikView May 2023?
QlikView 12.80: set a different Session Algorithm for QVP communication
Communication to QlikView server fails: Switching to HTTPS tunneling 
QlikView Client connection fails with Connected server OK, negotiations timed out Switching to HTTP tunneling No reply received  

Internal Investigation ID(s)

QV-24861

Environment

QlikView 

Qlik Sense supports Web Content Accessibility (WCAG 2.0 compliant).

When using the Qlik Sense hub, this is available by default, however, in a mashup, some work is needed from the mashup developer to make the mashup accessible.

This article provides an example of a mashup that is compliant with Web Content Accessibility. Find the attachment below. 

The example is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.

Environment

• Qlik Sense Enterprise on Windows 

Qlik Enterprise Manager (QEM) fails to monitor Qlik Replicate. 

The following issues can be observed:

• Disconnect of the Qlik Replicate Server 
• Message that the Qlik Replicate Server is not monitoring
• The underlying connection was closed
• Status changes from Monitored to Error to Monitored
• Server Connection Loss

Possible error messages:

• The underlying connection was closed: A connection that was expected to be kept alive was closed by the server.
• Failed to get monitoring data for server: Replicate_server_name. Message:'The operation has timed out'
• Failed to get tasks from server 'Replicate_server_name' : The operation has timed out

Environment

• Qlik Enterprise Manager versions 2023.5, 2023.11, and 2024.5
• Qlik Replicate for both Windows and Linux

Resolution

This is a known issue and Qlik is actively working on a patch. Please review the release notes for QB-26321 and QB-27571 for updates. 

Cause

QB-26321 and QB-27571

Internal Investigation ID(s) 

QB-26321 and QB-27571

To help Qlik customers manage costs more effectively, Qlik has developed the Qlik Snowflake Monitoring application, designed to provide invaluable insights about your Snowflake costs, usage, inventory, security, performance and contract utilization. This app utilizes Qlik's Associative Engine to connect directly to your Snowflake instance and reveal insights from Snowflake's detailed metadata, offering valuable information that traditional query-based tools and Snowflake's own reports are unable to provide.

Leveraging Qlik Application Automation, and Data Alerts, you can:

• Install* & update the app with a fully guided, click-through installer, using an out-of-the-box Qlik Application Automation template.
• Get alerted when new versions of the Snowflake Monitor are available using Data Alerts.

*Minor configuration is required on first run to create the required data connections.

Content:

• Part One: 'Qlik Snowflake Monitoring App Installer' templateoverview
• Features
• Note on manual install
• Part Two: Creating and setting up analytics data connections
• Snowflake connection
• Note on Snowflake authentication
• REST connection to repository
• Note on update compatibility
• Part Three: Set up a Data Alert to notify when a new version of the app is available
• Summary

Part One: 'Qlik Snowflake Monitoring App Installer' template overview

This automation template is a fully guided installer/updater for the Qlik Snowflake Monitor. Leverage this automation template to easily install and update this application. The application itself is community-supported; and it is provided through Qlik’s Open-Source Software GitHub and thus is subject to Qlik’s open-source guidelines & policies.

For more information, refer to the GitHub Repository.

Features

• Easy app installation and updates
• Create new spaces or use existing spaces
• Automatic setup of settings, roles, and permissions
• Always installs the newest version from Qlik's OSS GitHub
• Tags apps to easily track installations and versions
• Works with both user and capacity-based subscriptions
• Compatible with all Snowflake tenant levels

Note on manual install

If the monitoring app was installed manually (i.e. not through the application automation installer), then the app will not be detected as existing. The automation will install new copies side-by-side. Any subsequent executions of the automation will detect the newly installed monitoring application and check their versions. This is because the application is tagged with ‘QCS - QSM - {App Name}’ and ‘QCS – QSM - {Version}’ during the installation process through the automation. Manually installed applications will not have these tags and therefore will not be detected.

Part Two: Creating and setting up analytics data connections

The Qlik Snowflake Monitor requires two connections, one to your Snowflake instance to feed the data for your analytics, and one REST connection to the qlik-oss repository to run a version check on the monitor.

Snowflake connection

You will need to create a custom User, Role and Warehouse on your snowflake tenant. This is to ensure this user and role can see the monitoring details and can be monitored.

1. Update the credentials in the SQL script from GitHub 
2. Run the SQL as ‘ACCOUNTADMIN’ from your Snowflake tenant to create a warehouse to retrieve the relevant data. Make sure you change the password and store this securely.
3. Create a snowflake data connection in the Qlik analytics space into which the application was deployed, using the following details:
   
   
   • Server: The full hostname for the Snowflake account, not prefixed with http:// or https://
   • Port: Leave as default unless it needs changing.
   • Database: SNOWFLAKE
   • Schema: ACCOUNT_USAGE
   • Warehouse: QLIK_MONITORING_WH
   • Role: QLIK_MONITORING_ROLE
     
     

   For Authentication, this setup is defaulted to username & password.

   • Username: QLIK_MONITORING
   • Password: As specified in your configuration above
     
     

   Finally, you need to name the connection as follows:

   • Connection Name: SNOWFLAKE_MONITORING_DATA
     
     
   
   

    

Note on Snowflake authentication

If you wish to use an alternative authentication method, please follow the documentation accordingly on both Snowflake & Qlik.

REST connection to repository

The REST connection is used to fetch version details from the GitHub repository. On reload it will look for the the latest released version in github and check this against the version you have installed. You can later use this in ‘Part Three’ to create an alert when updates to the application are available. To create a REST connection the following information is required:

• URL: https://raw.githubusercontent.com/qlik-oss/qlik-snowflake-monitor/main/manifest.json 
• METHOD: GET
• Allow “WITH CONNECTION”: Enabled
• Connection Name: REST Monitoring Versioning API
  
  
  
  

Once these two connections have been set up, you can reload the application. The application has been created to accommodate Snowflake tenants of all sizes. If you have a small tenant, you will find the initial run of the load script can take around 30 minutes, and for larger tenants this can be over an hour or two. Subsequent runs will utilize cached QVDs that update daily to reduce reload times each subsequent day.

Note on update compatibility

If a new release of the application is made, occasionally a full reload of data is required, but generally, if the data schema is unchanged the existing QVDs will be maintained. This is through the use of versions in the names of the QVDs used to store the data.

Part Three: Set up a Data Alert to notify when a new version of the app is available

The application has the following two variables:

• vLatestVersion: The latest version of the app released on Qlik’s OSS GitHub.
• vIsLatestVersion: A Boolean of whether the app’s current version is equal to the latest version of the app released on Qlik’s OSS GitHub (1 if true, 0 if false).

To create a new Data Alert for updates to the monitoring app, follow these steps:

1. Right-click on a chart in the app, select Alerts and then Create new alert.
2. Clear out the defaults and provide the alert with a name such as Qlik Snowflake Monitor Update Available.
3. Select Add measure and select the fx icon to enter a custom expression. Enter the expression ’$(vLatestVersion)'. Ensure it is wrapped in single quotes, then provide the label for the expression Latest Version.
4. Select Add measure and select the fx icon to enter a custom expression. Enter the expression $(vIsLatestVersion), then provide the label for the expression Is Latest Version.
5. Confirm the Details & data tab resembles the following:
   
   
   
   
6. Navigate to the next tab, Conditions.
7. Set the Measure to Is Latest Version, the Operator to Equal to, and the Value to 0. This way, if the app is not the latest version (0), it will trigger the alert.
8. Confirm that the Conditions tab resembles the following:
   
   

   

6. Navigate to the Distribution tab and confirm that the alert is evaluated When data is refreshed.

Summary

The Qlik Snowflake Monitor can be easily installed by following these steps above. If you wish to find out more, check out this Ometis blog post and this Ometis Webinar to get a run through of the analytics this application can offer.

If you face any issues, please use the GitHub and raise an issue through the repository.

You may experience problems when executing actions with the MetaServlet API in the Talend Administration Center using the MetaServletCaller.sh or MetaServletCaller.bat scripts and the call doesn't work.

The error message you receive is:

Error: "error": “Username or password is wrong”,"returnCode": 3

Cause

The error arises because special characters in the username or password need to be escaped. Since JSON, the data format used by the MetaServlet API, does not support certain special characters without escaping.

Resolution

Use the control character backslash ("\") to escape special characters.

For Example

Password: passwor"d  the quotation mark is the special character that needs to be escaped using a backslash. 

Use passwor\"d to include the quotation mark in the password.

Related Content

For more information about Metaservlet, please check Qlik Talend Official Documentation
Metaservlet

Environment

Talend Administration Center 

Snowflake supports using key pair authentication for enhanced authentication security as an alternative to basic authentication (i.e. username and password). This article covers end-to-end setup for Key Pair Authentication in Snowflake and Qlik Replicate.

This authentication method requires, at minimum, a 2048-bit RSA key pair. You can generate the Privacy Enhanced Mail (i.e. PEM) private-public key pair using OpenSSL.

Qlik Replicate will use the ODBC driver to connect snowflake and ODBC is one of the supported clients which will support key pair authentication.

Let's assume, you decided to use key pair authentication for the Snowflake user which is used in Qlik Replicate to connect to Snowflake. You have to follow the below process to convert user authentication from basic to key pair.

Step 1: Generate the Private Key

You can generate either an encrypted version of the private key or an unencrypted version of the private key.

To generate an unencrypted version use the following command in the command prompt:

$ openssl genrsa 2048|openssl pkcs8 -topk8 -inform PEM -out rsa_key.p8 -nocrypt

To generate an encrypted version (which omits -nocrypt) use:

$ openssl genrsa 2048|openssl pkcs8 -topk8 -v2 des3 -inform PEM -out rsa_key.p8

In our example case, we generate an encrypted version of a private key.

We:

1. Open a command prompt
2. Run $ openssl genrsa 2048|openssl pkcs8 -topk8 -v2 des3 -inform PEM -out rsa_key.p8
3. Enter our password
4. And store the password to use in Qlik Replicate.

This generates a private key in PEM format:

Step 2: Generate a Public Key

From the command line, we generate the public key by referencing the private key. The following command assumes the private key is encrypted and contained in the file named rsa_key.p8.

When it requests a passphrase, use the same password that we generated in step 1.

openssl rsa -in rsa_key.p8 -pubout -out rsa_key.pub

This command generates the public key in PEM format:

Step 3: Store the Private and Public Keys Securely

Copy the public and private key files to a local directory for storage and record the path to the files. Note that the private key is stored using the PKCS#8 (Public Key Cryptography Standards) format and is encrypted using the passphrase you specified in the previous step.

However, the file should still be protected from unauthorized access using the file permission mechanism provided by your operating system. It is your responsibility to secure the file when it is not being used.

Step 4: Assign the Public Key to a Snowflake User

Describe the user to see current information. We can see that there is no public key assigned to the HDW user. Therefore, the user needs to use basic authentication.

Execute an ALTER USER command to assign the public key to a Snowflake user.

Step 5: Verify the User’s Public Key Fingerprint

Execute a DESCRIBE USER command to verify the user’s public key.

Step 6: Configure Qlik Replicate to Use snowflake Key Pair Authentication

1. Enter the snowflake server name and the username that we configured key pair authentication.
   
   
   
   
2. We need to set the below parameters to set the authentication method as SNOWFLAKE_JWT, passing the private key and password from step 1.
   
   
   
   
3. Try to do the test connection\browse the database and you can see a missing password error. We can't ignore the password in the endpoint UI and at the same time, we shouldn't enter the password as we are using keypair authentication.
   
   
   
   
4. You can key in a dummy password, such as dummy, dummy123, etc., in the UI to eliminate the missing password error.
   
   Finally, browse the database and do the test connection.
   
   

Environment

Qlik Replicate 
Snowflake Target

Question

How do you update the image used in the Preview Picture section in the HTML that is created when selecting Generate Doc as HTML?

You can update the image by editing the job in the designer view and then saving it.
For example, if you place a random component in the job designer, save the job, and select Generate Doc as HTML, the image used in the Preview Picture section will update showing the newest image of your job.

If you are looking for how to generate detailed documentation in HTML of the Jobs or Routes, please refer to Qlik Talend Official Documentation for more information.
Generating-html-documentation

Environment

Talend Studio 

This article provides instructions on how to measure data transfer speeds when working with Qlik Data Gateway - Direct Access.

The information in this article is provided as-is and will be used at your discretion. Depending on the tool(s) used, customization(s), and/or other factors, ongoing support on the solution below may not be provided by Qlik Support.

Instructions

1. Log in to the Data Gateway Server
2. Using the attached PowerShell file (Create-Dummy-Data-File.ps1), create a 1 GB large file using the following command:
   
   .\Create-Dummy-Data-File -Size 1024
   
   You can increase the file size to 2 GB by using 2048 instead.
   
   The PowerShell script will create a QVD file for testing purposes. The file includes randomly generated data designed to avoid network compression. It is recommended to generate the file on the Gateway server itself and upload it from there.
   
   The file does not include any usable or valid data and should be deleted after the test, both from the local storage and Qlik Cloud. 
   
   
3. With the file created, log in to your Qlik Cloud. Do so from the Data Gateway - Direct Access gateway server you want to benchmark.
   
   
   1. Open the Qlik Cloud hub and select Add Dataset or Create Data Set
   2. A  window will open, select Upload Datafile 
   3. Select the QVD that was just created, and indicate the Space to upload the file. Do not yet upload the file.
   4. Open the browser developer tools.
   5. With the developer tools open, select Upload to begin the upload process.
   6. Wait until the file is uploaded, then collect the har file (read more here). 
      
      
4. Repeat the above two to three times, replacing the data file during the upload.
5. Once completed, open the collected har files and search for temp-contents. You can use the file requests to calculate your results.
   
   In the below example, we would consider the last five requests:
   
   
   
   

Environment

• Qlik Cloud
• Qlik Data Gateway

Filter Panes and List Boxes in a Qlik App can be configured as a Radio Button menu, allowing only one value to be selected.

1. Begin editing the sheet with your Filter Pane; click Edit Sheet
2. Select your Filter Pane, open the Data menu section and click the Field name
3. Expand the Presentation menu
4. Tick the Checkbox mode option
   
   
   
5. Open the Fields menu
6. Select the field you are using in your Filter Pane
7. Click the Gears, opening the Field Settings
   
   
   
   
8. Tick the Always one selected value checkbox
   
   
   
   
9. You now have a Radio Button menu!
   
   

Environment

• Qlik Cloud Analytics
• Qlik Sense Enterprise on Windows

Related Content

• Enabling checkbox mode (help.qlik.com)

Users experiencing intermittent errors where the App load will be stuck in initializing for two minutes before advancing and the Hub will display the following error:

Connection lost. Make sure that Qlik Sense is running properly. If your session has timed out due to inactivity, refresh to continue working.

When this issue occurs the behavior will be seen by all users and a restart of the Qlik Sense repository services will restore normal operation (though in some deployments temporarily)

A HAR file or review of the developer tools of the Hub will show the Hub attempting to establish a connection to the qrsData WebSocket and then failing with the error message on the Hub and app load resuming once the WebSocket fails.

Additionally, if the Trace > Audit logs for the Proxy service are set to Debug the following error will be seen:

Connection <Connection_ID> has been transferred to a streaming state to send a single error message <client_IP_address> <host>:4239

Port 4239 is the port used by the qrsData WebSocket.

Environment

• Qlik Sense Enterprise on Windows

Cause

This behavior was discovered in environments running the Tenable penetration test against the Qlik Sense servers, although this could be caused by other penetration testing software or other code that meets the conditions to cause the behavior.

The error is caused by a combination of timing and error handling in which a large number of bad requests are made without certificates, such that the connection is closed before Qlik Sense finishes validating the request. In this scenario, Qlik Sense does not handle the error gracefully and requires a restart of the Repository service to recover.

The error condition does not come up under normal operations due to how quickly the validation runs but the rapid requests from penetration test can lead to the error condition described.

Qlik will release a fix in a future patch that will allow Qlik Sense to handle this scenario gracefully. 

Workaround:

Unless specifically targeting Qlik Sense (including maintenance where applicable), exclude Qlik Sense from penetration tests. 

An alternative is a scheduled restart of the Qlik Sense services following the completion of the penetration test.

Internal Investigation ID(s):

QB-29033

Related Content

• Anti-virus, Endpoint detection and response and Advanced Threat Prevention exclusions for Qlik product deployments 
• Manual Start and Stop order of Qlik Sense services