You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great if we could disable SameSite=Lax and set it to None in session cookies, or disable sending X-Frame-Options with responses - although that last one can be handled by our proxy.
Expected Behavior
Allow of setting those values through config or environment variables, just like MINIO_BROWSER_CONTENT_SECURITY_POLICY.
Allow configuration of this attribute via Environment Variable or Configuration Setting, possibly as:
Environment
Configuration
MINIO_BROWSER_COOKIE_SAMESITE=None
mc admin config set browser cookie_samesite="None"
MINIO_BROWSER_FRAME_DENY=off
mc admin config set browser frame_deny="off"
Steps to Reproduce (for bugs)
Open console in embedded iframe
Context
We have a cluster management panel which opens various solution management pages in iframe. This includes Traefik dashboards, Prometheus, Grafana etc. Lately we've added MinIO console to that list but due to cookies being sent with SameSite=lax and that iframe doesn't start top-level navigation, session token is not set by browser and console is only usable in top-level tab or window.
Regression
No
Your Environment
MinIO version used (minio --version):
minio version RELEASE.2024-12-18T13-15-44Z (commit-id=16f8cf1c52f0a77eeb8f7565aaf7f7df12454583)
Runtime: go1.23.4 linux/amd64
License: GNU AGPLv3 - https://www.gnu.org/licenses/agpl-3.0.html
Copyright: 2015-2024 MinIO, Inc.
Server setup and configuration:
Running as tenant on Kubernetes cluster with MinIO Operator v6.0.4
The text was updated successfully, but these errors were encountered:
After further investigation it looks like that setting SameSite=None might classify this cookie as "Third-party" and therefore still block it.
In our case one sensible solution would be to migrate all console related domain entries to be same origin as our root dashboard domain, so cookies won't be considered as cross-origin.
It would be great if we could disable
SameSite=Lax
and set it toNone
in session cookies, or disable sendingX-Frame-Options
with responses - although that last one can be handled by our proxy.Expected Behavior
Allow of setting those values through config or environment variables, just like
MINIO_BROWSER_CONTENT_SECURITY_POLICY
.Current Behavior
Currently
Lax
is hard-coded value:console/api/utils.go
Line 173 in 656d807
Possible Solution
Allow configuration of this attribute via Environment Variable or Configuration Setting, possibly as:
MINIO_BROWSER_COOKIE_SAMESITE=None
mc admin config set browser cookie_samesite="None"
MINIO_BROWSER_FRAME_DENY=off
mc admin config set browser frame_deny="off"
Steps to Reproduce (for bugs)
iframe
Context
We have a cluster management panel which opens various solution management pages in
iframe
. This includes Traefik dashboards, Prometheus, Grafana etc. Lately we've added MinIO console to that list but due to cookies being sent withSameSite=lax
and thatiframe
doesn't start top-level navigation, session token is not set by browser and console is only usable in top-level tab or window.Regression
No
Your Environment
MinIO version used (
minio --version
):Server setup and configuration:
Running as tenant on Kubernetes cluster with MinIO Operator v6.0.4
The text was updated successfully, but these errors were encountered: