Third Party Cookies Google Chrome Phase out

[IsaacBlanco]

With Google Chrome's recent change to remove third-party cookies this year, many solutions responsible for running embedded content are being affected.

In reviewing the Sisense documentation, it appears that alternatives such as utilizing Web Access Tokens (WAT) or employing the same domain for various apps behind specific paths are suggested. However, both solutions have limitations hindering their implementation:

1. WAT, as stated in the documentation, only applies to registered users with the viewer role. This raises concerns about accessibility for users with Administrator or Designer roles. Is there an official solution available for these user types?

2. Regarding domains, the proposed solution of consolidating apps under a single domain and path poses challenges for solutions with multiple custom domains.

Considering Google Chrome's plan to remove all third-party cookies for 100% of its users by the end of the year, and the potential for other browsers to follow suit, it's crucial to explore viable alternatives. Is there a plan to adopt the CHIPS initiative for cookie management in the near future, or are there existing solutions available for testing the transition?

[olegfil · Accepted solution]

hi @IsaacBlanco ,

Thank you for bringing this up. We are aware of the changes related to the third-party cookies that are planned to be implemented this year. We're currently working on enabling CHIPS support for embedding via Iframe. Once implemented, it will be added to the release notes.