Office 365 Sharepoint Connector (Qliksense August 2022) Error

[diego_rueda]

Hi,

I had installed the latest version of qliksense enterprise for windows (August 2022 Initial release) and we are having problems with Office 365 sharepoint while we are introducing parameters of connection. In my case i'm trying to access using a sharepoint Url, a subpath and the type of connection but the system is returning an error after click on Authenticate button.

We have Web connectors and this connector works with this configuratio but i have to use the new connector's version included in qliksense enterprise.

The error is "Error Retrieving the URL to authenticate: ENCRYPTION_KEY_MISSING-you must manually set an encryption key before creating new connections"

Anybody can help us with this issue?.

Thanks

[denisb]

Same issue 😞

Need help, too. 

[Given-Sekgotodi]

Hi Diego

I am not sure if you have checked Qlik Help article to resolve. 

Check this article : https://help.qlik.com/en-US/connectors/Content/Connectors_Home/Setting-encryption-key.htm

Not sure if this will help but should provide some insights 

Cheers

[Rakesh_HB · Accepted solution]

Hello,

Please check this on how to generate the Encryption key;

• ENCRYPTION_KEY_MISSING while connecting to Google Drive in Qlik Sense Enterprise on Windows 

When applicable please mark the correct/appropriate replies as "Solution Accepted"... Cheers!

[Ken_T]

replies on this post do not seem to address how to resolve this issue on an enterprise qlik system...  can anyone elaborate? why doesn't the creation of the connection, in the enterprise HUB, pop up and allow the user to authenticate and create the token/key that the connection needs?

[Ken_T]

 report, once the key is generated and saved on all the rim nodes, then the SP connection works like the new qlik saas SharePoint connector. It is better than the old web connector process. user authenticates, gets a user key/token, this is stored in the connection. One connection for the entire site sub site path, instead of many for each single file by ID. it behaves more like a folder connection in the load script, using the file name.