Qlik Automate's ServiceNow connector is moving from username and password authentication to OAuth 2.0. This change aligns with security best practices and ServiceNow's own recommendations for third-party integrations, eliminating the need to store credentials in plain text and providing more granular, revocable access control. When will this change be made? The change will go into effect on the 23rd of June, 2026. What action do I need to take? Existing connections that use username and password authentication will need to be re-authenticated using OAuth 2.0. Complete the re-authentication steps as outlined in this blog post on the 23rd of June to prevent possible service interruptions. How do I switch my ServiceNow connection to OAuth 2.0? ServiceNow provides guidance on each stage of the OAuth 2.0 setup. See the following for details: OAuth 2.0 Overview Set up OAuth OAuth Inbound OAuth Inbound and Outbound authentication Enable OAuth with inbound REST To migrate your Qlik Automate connector, first prepare ServiceNow by configuring OAuth 2.0, then re-authenticate Qlik Automate on the 23rd of June. Before you begin, make sure you have Admin access to your ServiceNow instance and Admin or Owner access to your Qlik Cloud tenant and the relevant Qlik Automate automation. Open the Application Manager in ServiceNow: The OAuth 2.0 plugin must be available in your ServiceNow instance. Log in to your ServiceNow instance. Click the All button in the top-left navigation bar and search for Application Manager. Select Application Manager from the results under Admin Center. In the Application Manager, use theSearch your licensed applications and plugins field to search for OAuth. The ServiceNow products OAuth tile will appear in the results. Click the OAuth tile to expand it, then install the OAuth 2.0 plugin (Plugin ID: com.snc.platform.security.oauth). Wait for the installation to complete before proceeding. Navigate to Inbound Integrations: Click the All button again and search for Inbound Integrations. Select it from under System OAuth in the results. Create a new OAuth application endpoint: Click the New Integration button on the right. On the connection type screen, select OAuth – Authorization code grant. Configure the application by providing a Name, the Redirect URL, and the required scopes. When prompted for a Redirect URL, use the callback URL provided by Qlik Automate during the connection setup. This URL must exactly match what is registered in ServiceNow. Save the Client ID and Client Secret; they are required for the next step. Click Save. Re-authenticate the connector in Qlik Automate This step can only be carried out after the change on the 23rd of June, 2026. In Qlik Automate, add a new ServiceNow connection. Enter your ServiceNow instance domain (format: https://[domain].service-now.com/). Provide the Client ID and Client Secret previously recorded. Follow the on-screen authentication flow to complete the OAuth authorisation. If you encounter issues during the migration, please contact Qlik Support or visit the Qlik Community for assistance. When raising a support case, include your ServiceNow instance domain and the error message you are seeing. Thank you for choosing Qlik,Qlik Support ...View More

Snowflake is rolling out stronger authentication requirements as part of their platform security initiative. Starting May 2026, new connections using only username and password will no longer be accepted, and all existing password-only connections will stop working between August and October 2026. For the full rollout schedule, see Snowflake's authentication enforcement timeline. If your Qlik Sense Cloud Analytics,Qlik Sense Enterprise on Windows, or QlikView environment connects to Snowflake, you will need to update those connections to use either key-pair authentication or OAuth before this change takes effect. Who does this apply to? This applies to any Qlik Cloud Analytics, Qlik Sense Enterprise on Windows, and QlikView connection to Snowflake, where the authentication method is set to Username and Password only. Connections that already use key-pair authentication or OAuth do not need to change. To check your connections, review the Data connections and look for any Snowflake connections using username and password authentication. What are my migration options? There are two supported authentication methods you can migrate to. Key-Pair Authentication Key-pair authentication uses an RSA private/public key pair assigned to the Snowflake user account. It is the most straightforward migration path and does not require an identity provider. This option is recommended for most customers. For setup steps, see Snowflake key-pair authentication documentation and the Qlik Snowflake connector guide. OAuth OAuth integrates with your existing identity provider (such as Okta or Azure AD) and is well-suited for organisations that want centralised access control and token-based authentication. It requires an OAuth security integration to be configured in Snowflake. See theQlik Snowflake connector guide and Snowflake OAuth documentation. OAuth support for Snowflake will be introduced toQlik Sense Enterprise on Windows with our Q2 2026 release. If you have any questions, we are, as always, happy to assist. Reply to this blog post or take your queries to our Support Chat. Thank you for choosing Qlik,Qlik Support ...View More

Hello Qlik Cloud users and admins, We’ve enhanced the Qlik Cloud Status page subscription experience to give you more control over the notifications you receive. Previously, subscribing meant you received incident and maintenance notifications for all Qlik Cloud regions. With the updated Statuspage experience, you can now choose specific Qlik Cloud regions you want to follow. This helps reduce unnecessary notifications in your inbox and puts the focus on the Qlik Cloud deployment regions you have active tenants in. How do I subscribe or modify my current subscription? To subscribe: Visitstatus.qlikcloud.com ClickLog Inin the top right of the pageand authenticate with your Qlik ID ClickSubscribe to Updates Select your preferred notification method (Email or RSS feed) Confirm the method Choose which deployment region you wish to be notified for ClickSave To update your preferences: Visitstatus.qlikcloud.com ClickLog Inin the top right of the pageand authenticate with your Qlik ID ClickSubscribe to Updates Select your preferred notification method (Email) Enter the email address associated with your subscription and clickSubscribe via Email; this will send a One-Time Passcode (OTP) to your registered email address and may prompt a CAPTCHA Complete the CAPTCHA (if applicable) and clickSubscribe to Update Retrieve the One-Time Passcode (OTP), then enter your email address and your OTP ClickVerify OTP and Subscribe, andcomplete the CAPTCHA Select or deselect the Qlik Cloud regions you want to follow Save your updated preferences For a full guide, see Qlik Cloud and Qlik Talend Cloud Status. Thank you for choosing Qlik,Qlik Support ...View More

Hi everyone, Want to stay a step ahead of important Qlik support issues? Then sign up for our monthly webinar series where you can get first-hand insights from Qlik experts. Next Thursday, May 28 Qlik will host another Techspert Talks session and this time we are looking at Monitoring Qlik Cloud Capacity. But wait, what is it exactly?Techspert Talks is a free webinar held on a monthly basis, where you can hear directly from Qlik Techsperts on topics that are relevant to Customers and Partners today. In this session we will cover: Understanding capacity usage Explore the reporting app Tips for managing consumption Choose the webinar time that's best for you The webinar is hosted using ON24 in English and will last 30 minutes plus time for Q&A.Hope to see you there!! ...View More

The following two Qlik Talend Administration Centersecurity issues have been identified and subsequently resolved. Patches are already available. URL access control vulnerability (CVE-2026-9057) A broken access control issue has been identified inQlik Talend Administration Center, which allows a user withViewpermission to modify the Qlik Talend Studio update URL. Affected Software All versions of Qlik Talend Administration CenterbeforePatch_20251121_QTAC-1471_R2025-11_v1-8.0.1. SeeSecurity fix for Qlik Talend Administration Center URL access control vulnerability (CVE-2026-9057)for details. Cross-site scripting vulnerability (CVE-2026-9056) A stored cross-site scripting security issue in theQlik Talend Administration Centerhas been identified. Affected Software All versions of Qlik Talend Administration Center before Patch_20260123_QTAC-1883 (cumulative patch)_R2026-01_v1-8.0.1 are affected. SeeSecurity fix for Qlik Talend Administration Center cross-site scripting vulnerability (CVE-2026-9056)for details. Recommendation Upgrade at the earliest. The following table lists the patch versions addressing the vulnerabilities. Always update to the latest version. Before you upgrade, check if a more recent release is available. Product Patch Release Date Qlik Talend Administration CenterURL access control vulnerability QTAC-1471 November 21, 2025 Qlik Talend Administration Centercross-site scripting vulnerability QTAC-1883 January 23, 2026 Thank you for choosing Qlik,Qlik Support ...View More

Qlik introduced a change in how automation permissions are handled for the Analytics Admin role. When was the change introduced? The change is already live as of the 11th of May, 2026. What does that mean for me? Analytics Admins can now claim ownership of another user's automation. After claiming ownership, they can make necessary changes to it and enable the automation. However, they can no longer transfer ownership to another user. How do I claim ownership of an automation? As an Analytics admin, to claim ownership of an automation: Navigate to the Automations section in the Administration Console Locate the automation you want to claim ownership of, and click theActionsmenu (...) Choose Claim ownership This behavior change only applies to Analytics Admins. Tenant admins can still transfer ownership to any user with the appropriate access rights in the tenant. If you have any questions, we're happy to assist. Reply to this blog post or take your queries to our Support Chat. Thank you for choosing Qlik,Qlik Support ...View More

Don't miss our latest Q&A with Qlik! Pull up a chair and chat with our panel of experts to help you get the most out of your Qlik experience. WATCH HERE ...View More

Hi everyone, Want to stay a step ahead of important Qlik support issues? Then sign up for our monthly webinar series where you can get first-hand insights from Qlik experts. The Techspert Talks session from April looked at Migrating QlikView to Qlik Cloud. But wait, what is it exactly? Techspert Talks is a free webinar held on a monthly basis, where you can hear directly from Qlik Techsperts on topics that are relevant to Customers and Partners today. In this session we will cover: Converting QlikView documents to Sense Apps Qlik Cloud Advantages Migration Tools Click here to see the presentation ...View More

Edited May 4th, 2026: Added mitigation article, published on the 4th of May. Beginning on April 14, 2026, multiple QlikView customers experienced outages and intermittent disruptions within their QlikView environments. These incidents coincided with the deployment of Microsoft’s April 2026 security patches to Domain Controllers, which affected QlikView Server Service (QVS) communications over port 4747. The Microsoft patches introduced changes targeting Kerberos authentication and RC4 encryption. See Addendum for a list of patches. As a result, QlikView environments where RC4 remained enabled (such as at the domain account or Windows server level) became unstable or non-functional. The impact on QlikView may include, but is not limited to: Failed QlikView Distribution Server distribution tasks with an error code indicating an Authentication Failure. "No Server" message on the QlikView AccessPoint with an error message in the Web server log indicating that the Web server cannot connect to the QlikView Server. Failed Qlik NPrinting distributions to QlikView using a QVP Connection. Problems accessing the QlikView Server settings from the QlikView Management Console, or failures for the QlikView Server to come online after a restart. What can be done to mitigate this issue? We've published an article to help address the issue. See QlikView server communication interruptions following Microsoft Windows RC4 cipher suite deprecation. Information in the article is based on Microsoft's remediation steps and has been adjusted and expanded to include QlikView-specific instructions. For the original, seeDetect and remediate RC4 usage in Kerberos | learn.microfot.com. What action is Qlik taking? RC4 support was deprecated starting with the May 2024 release of QlikView. The root cause in these cases stems from legacy configurations where RC4 remained enabled in the environment, rather than a defect in QlikView itself. No code changes are planned at this time, though improvements to diagnostic logging are under consideration. Addendum Microsoft Patches: Windows Server 2022 (DC): KB5082142 Windows Server 2019 (DC): KB5082123 Windows Server 2016 (DC): KB508208 If you have any questions, we're happy to assist. Reply to this blog post or take your queries to our Support Chat. Thank you for choosing Qlik,Qlik Support ...View More

Salesforce is rolling out mandatory security updates to how connected apps handle OAuth authentication. What does this mean for me? To keep your Qlik Automate Salesforce connector working after Tuesday, 5th May 2026, you'll need to take a quick, one-time action: update a setting in your connection and re-authenticate to Salesforce. This cannot be done automatically, nor can it be done before the release. A manual step is required on or after the 5th of May. Why is this happening? Salesforce has updated its OAuth security requirements for connected apps. You can read Salesforce's full announcement here: Mandatory Security Updates for Connected Apps. Qlik Automate has updated the Salesforce connector to comply with these new security requirements. However, because of the nature of this change, existing connections cannot be migrated automatically. What action do I need to take? Follow these steps after the release on Tuesday, the 5th of May: Open your Salesforce connection settings, navigate to the Salesforce connection in Qlik Automations,and open its configuration. Add your domain. In the connection settings, locate the Enhanced_domain field (an existing input field) and enter your Salesforce org's custom domain.Make sure to include the "my" suffix if your domain has it. By using this, the 'environment' input is ignored. Format: https://{enhanced_domain}.salesforce.com.If you're unsure of your domain, you can find it in your Salesforce org under Setup → My Domain. Re-authenticate. Once your domain is entered, you'll be prompted to log in to Salesforce again and authorize the updated app. Complete the login flow to re-establish the connection. Verify the connection. Run a test automation that uses the Salesforce connection to confirm everything is working correctly. What happens if I don't act? If you don't complete these steps after the release date, your Salesforce automations will stop working and return a 401 Unauthorized error. No data will be lost, but you will need to complete the steps above to restore access. If you have any questions, we're happy to assist. Reply to this blog post or take your queries to our Support Chat. Thank you for choosing Qlik,Qlik Support ...View More