- Newest
- Most votes
- Most comments
It turns out that even though quicksight is sending a bunch of cookies as part of the embedded dashboard, the dashboard itself functions fine if the browser blocks those cookies (which it does in Safari and sometimes in Chrome.) So, ¯_(ツ)_/¯
Hello,
I understand that you are enquiring about embedding Quicksight dashbaords to have cookies for partitioning users. In Quicksight embedding currently there are two types of embedding supported Registered User Embedding[1] and Anonymous Embedding[2].
-
Registered User Embedding: This involves embedding dashboards for users who are authenticated through your system. You can apply row level security (RLS) and column level security (CLS) for fine grained access control for users.
-
Anonymous Embedding: This option is to let users use without having them register to Quicksight. You can share your dashbaords to any number of users via your application.
Both the options above are for user authentication purposes and session management. In order to better understand your use case and scenario of your users authetication and need of CHIPS (Cookies Having Independent Partitioned State) I would request you to raise a support case with AWS so that resource based troubleshooting can be done and suggest a possible workaround.
Thank you!
References:
[1] https://docs.aws.amazon.com/quicksight/latest/user/embedded-analytics-dashboards-for-authenticated-users.html
[2] https://docs.aws.amazon.com/quicksight/latest/user/embedded-analytics-dashboards-for-everyone.html
Relevant content
- asked 2 years ago
- asked 2 months ago
- asked 3 years ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 2 months ago
This is orthogonal to authentication. In both cases, quicksite uses several cookies, and doesn't set partitioned attribute on them, and therefore they run afoul of the CHIPs rules for 3rd party cookies.