-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
iFrame is not accessible on incognito chrome window #87901
Comments
Pinging @elastic/kibana-security (Team:Security) |
Pinging @elastic/kibana-core (Team:Core) |
I think this is behavior from chrome that we don't have any control over. Accessing the sessionStorage from an iframe seems considered as accessing third party cookies for chrome, and is disabled by default in anonymous mode, for security reasons. Apparently, workaround is to manually enabled third party cookies in anonymous mode from chrome's setting page. User will need to check We may need to document that somewhere, but that will be the only thing we can do. Manipulating the sessionStorage is mandatory for Kibana to work. |
I'm not sure if this is feasible or not, but it would be great if we could test for this when Kibana is bootstrapping the client-side, and display a usable Fatal Error instead |
Yea, we should add some preflight checks before bootstrapping the client-side and display a clear error in that case. |
I think |
Google Chrome seems to treat direct access to "localStorage" in an iframe in incognito as a "third party cookie" and blocks it (see [1]). [1] elastic/kibana#87901 (comment)
Closing this in favor of #121189, which appears to be reporting the same behavior |
Kibana version: 7.11.0 latest snapshot
Elasticsearch version: 7.11.0 latest snapshot
Server OS version: darwin_x86_64
Browser version: chrome latest (incognito window)
Browser OS version: OS X
Original install method (e.g. download page, yum, from source, etc.): from staging
Describe the bug: If user tries to open iFrame from Kibana in an incognito window - Kibana displays
Please note safari/firefox private windows don't have this problem. iFrame is also accessible on regular (not incongnito) window
Please note it works fine if user turns off the setting which blocks third party cookies on chrome incognito window -
Errors in browser console (if relevant):
The text was updated successfully, but these errors were encountered: