Skip to main content
Announcements
Qlik Community Office Hours, March 20th. Former Talend Community users, ask your questions live. SIGN UP
Andre_Sostizzo
Digital Support
Digital Support

Development that use cross-site resources may encounter issues when Chrome version 80 is released in the month of February 2020.

Development that use cross-site resources may encounter issues when Chrome version 80 is released in the month of February 2020. An example of when issue may occur is when using  "domReady".  (https://www.cdnpkg.com/require-domReady)

The following may be registered in the Google Chrome Development Tools:

"A cookie associated with a cross-site resource at ....[URL]... was set without the `SameSite` attribute. It has been blocked, as Chrome now only delivers cookies with cross-site requests if they are set with `SameSite=None` and `Secure`. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032."

Even though this comes from the Chrome console, other browsers as Mozilla and Edge may also displaying similar warnings. 

The above may currently happen on the latest Qlik Sense Enterprise and QlikView releases.

This is cause by a new CORS security standard/feature that browsers are now enforcing, or beginning to enforce as developers begin to opt in. More information is available here https://www.chromestatus.com/feature/5088147346030592 and here https://www.chromestatus.com/feature/5633521622188032 as the above error mentions.

R&D is currently working on a solution, and updates regarding this will be posted here once this information becomes available.

Known Workaround(s):

  • For now, the SameSite security feature is not being enforced by default. If you are using Chrome versions 79 and below, the default setting for SameSite is "default", which is equivalent to "disabled". You can check it here chrome://flags/#same-site-by-default-cookies. In Chrome versions 80 and newer, "default" will be equivalent to "enabled", which enforces this security setting and will require an update to Qlik Sense and QlikView to prevent requests from being blocked. Until an update is provided, a temporarily workaround would be to change the SameSite setting to "disabled".
  • Edit the domain policy for where a list of specific domains are allowed for the legacy SameSite behavior to be used. See Cookie Legacy SameSite Policies.
 
NOTE:
  • Qlik will have official patches and service releases for both Qlik Sense and QlikView available on the Wednesday's, Feb 12th 2020 delivery.
  • Licensee patches will be available on demand for Qlik Sense as of Feb 3rd 2020, please contact Qlik Support.

 

Reference: https://support.qlik.com/articles/000092955

14 Comments