Superset : UserWarning: The 'session' cookie is too large #30302
Unanswered
haripriyacv
asked this question in
Q&A / Help
Replies: 1 comment 5 replies
-
To resolve the 'session' cookie size issue in Apache Superset version 3 when using Keycloak for authentication, you can switch to server-side sessions. This can be done by configuring the session to use a backend like Redis. Here is how you can modify the # Whether to use server side sessions from flask-session or Flask secure cookies
SESSION_SERVER_SIDE = True
# Example config using Redis as the backend for server side sessions
from flask_session import RedisSessionInterface
SESSION_TYPE = "redis"
SESSION_REDIS = Redis(host="localhost", port=6379, db=0) This configuration will store session data on the server side, reducing the size of the session cookie sent to the client [1]. |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
With Apache Superset version 3 and up, I am facing issues with session cookies. Authentication is configured through keycloak. I am facing the following error for a few users.
superset[8715]: /apps/venv/lib64/python3.9/site-packages/werkzeug/sansio/response.py:261: UserWarning: The 'session' cookie is too large: the value was 4059 bytes but the header required 40 extra bytes. The final size was 4099 bytes but the limit is 4093 bytes. Browsers may silently ignore cookies larger than this.
My session configuration in config.py is as below:
Never faced this issue with version 2. Please help urgently.
Beta Was this translation helpful? Give feedback.
All reactions