Skip to main content
Announcements
July 15, NEW Customer Portal: Initial launch will improve how you submit Support Cases. READ MORE

Qlik Sense Enterprise on Windows: Error retrieving the URL to authenticate: ENCRYPTION_KEY_MISSING

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Rakesh_HB
Support
Support

Qlik Sense Enterprise on Windows: Error retrieving the URL to authenticate: ENCRYPTION_KEY_MISSING

Last Update:

Dec 18, 2023 4:55:59 AM

Updated By:

Sonja_Bauernfeind

Created date:

Nov 1, 2022 4:04:15 AM

Some connectors require an encryption key before you create or edit a connection. Failing to generate a key will result in:

Error retrieving the URL to authenticate: ENCRYPTION_KEY_MISSING - you must manually set an encryption key before creating new connections.

 

Encryption 1.png

Environment

Qlik Sense Desktop February 2022 and onwards
Qlik Sense Enterprise on Windows February 2022 and onwards
all Qlik Web Storage Provider Connectors 
Google Drive and Spreadsheets Metadata 

 

Resolution

PowerShell demo on how to generate a key:

# Generates a 32 character base 64 encoded string based on a random 24 byte encryption key
function Get-Base64EncodedEncryptionKey {
$bytes = new-object 'System.Byte[]' (24)
(new-object System.Security.Cryptography.RNGCryptoServiceProvider).GetBytes($bytes)
[System.Convert]::ToBase64String($bytes)
}

$key = Get-Base64EncodedEncryptionKey
Write-Output "Get-Base64EncodedEncryptionKey: ""${key}"", Length: $($key.Length)"

Example output:

Get-Base64EncodedEncryptionKey: "muICTp4TwWZnQNCmM6CEj4gzASoA+7xB", Length: 32

 

Qlik Sense Desktop

This command must be run by the same user that is running the Qlik Sense Engine Service (Engine.exe). For Qlik Sense Desktop, this should be the currently logged-in user.

Do the following:

  1. Open a command prompt and navigate to the directory containing the connector .exe file. For example:

    "cd C:\Program Files\Common Files\Qlik\Custom Data\QvWebStorageProviderConnectorPackage"

  2. Run the following command:

    QvWebStorageProviderConnectorPackage.exe /key {key}

    Where {key} is the key you generated. For example, if you used the OpenSSL command, your key might look like: QvWebStorageProviderConnectorPackage.exe /key zmn72XnySfDjqUMXa9ScHaeJcaKRZYF9w3P6yYRr

  3. You will receive a confirmation message:

    Info: Set key. New key id=qseow_prm_custom.

    Info: key set successfully!

 

Qlik Sense Enterprise on Windows

The {sense service user} must be the name of the Windows account which is running your Qlik Sense Engine Service. You can see this in the Windows Services manager. In this example, the user is: MYCOMPANY\senseserver.

Do the following:

  1. Open a command prompt and run:

    runas /user:{sense service user} cmd. For example:runas /user:MYCOMPANY\senseserver

  2. Run the following two commands to switch to the directory containing the connectors and then set the key:

    1. "cd C:\Program Files\Common Files\Qlik\Custom Data\QvWebStorageProviderConnectorPackage"

    2. QvWebStorageProviderConnectorPackage.exe /key {key}

      Where {key} is the key you generated. For example, if you used the OpenSSL command, your key might look like: QvWebStorageProviderConnectorPackage.exe /key zmn72XnySfDjqUMXa9ScHaeJcaKRZYF9w3P6yYRr

  3. You should repeat this step, using the same key, on each node in the multinode environment.

  4. Encryption keys will be stored in: "C:\Users\{sense service user}\AppData\Roaming\Qlik\QwcKeys\"

    For example, encryption keys will be stored in "C:\Users\QvService\AppData\Roaming\Qlik\QwcKeys\"

Always run the command prompt while logged in with the Qlik Sense Service Account which is running your Qlik Sense Engine Service and which has access to all the required folders and files. 

Cause

This security requirement came into effect in February 2022. Old connections made before then will still work, but you will not be able to edit them. If you try to create or edit a connection that needs a key, you will receive an error message: Error retrieving the URL to authenticate: ENCRYPTION_KEY_MISSING) - you must manually set an encryption key before creating new connections.

 

Related Content

Setting an encryption key

 

 

Labels (1)
Comments
joshishu
Contributor II
Contributor II

@Rakesh_HB  @Sonja_Bauernfeind last year with above shared method I was able to create connection with sharepoint but this year getting attached error requesting if any help can be provided

joshishu_0-1710421157826.png

 

Ken_T
Specialist
Specialist

@joshishu 
that error AADSTS7000112 might be a set up problem on the teams/sharepoint side, per microsoft.
https://learn.microsoft.com/en-us/answers/questions/1259334/unable-to-sign-into-microsoft-teams-erro...

reach out to your Teams and SharePoint admins and see if they have disabled / changed anything related to this, since it last worked for you. 

joshishu
Contributor II
Contributor II

@Ken_T as per the erroe message Qlik Web Connectors (Office 365 Sharepoint)) is disabled. how we can enable same at our end 

Ken_T
Specialist
Specialist

the Microsoft page has some steps that might be helpful for your TEAMS / SHAREPOINT admins.  the error indicates that this has probably been disabled on Teams / SharePoint, not in the qlik system.

reach out to whoever in your company administers teams and sharepoint. they may be able to review the Microsoft information on that page  and determine best way to enable this connection to work.

telling them that it used to work, should help.... If they tracked their changes in a change management tool, they may be able to find how it used to be configured, when it worked previously for you

hope this info helps

AlexOmetis
Partner Ambassador
Partner Ambassador

@joshishu When you first set up the connector for SharePoint, an application is registered in your Azure AD (Entra ID) - you would see this in the Azure portal under "Enterprise applications" if you have access to that. It appears that someone has disabled this application - you would need to speak to your Azure administrator to get it re-enabled.

Version history
Last update:
‎2023-12-18 04:55 AM
Updated by: