Public bug reported: We still use SESSION_ENGINE = 'django.contrib.sessions.backends.signed_cookies' as default. There is a limitation on the length of cookies and using keystone v3 can hit this limitation.
We configure the local memory for session storage django.core.cache.backends.locmem.LocMemCache, but according to the django documentation [1], this is only effective when django.contrib.sessions.backends.cache is used as SESSION_ENGINE. I think it is better to switch the default SESSION_ENGINE to django.contrib.sessions.backends.cache. [1] https://docs.djangoproject.com/en/1.11/topics/http/sessions /#configuring-the-session-engine ** Affects: horizon Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1736021 Title: default SESSION_ENGINE is still signed_cookies Status in OpenStack Dashboard (Horizon): New Bug description: We still use SESSION_ENGINE = 'django.contrib.sessions.backends.signed_cookies' as default. There is a limitation on the length of cookies and using keystone v3 can hit this limitation. We configure the local memory for session storage django.core.cache.backends.locmem.LocMemCache, but according to the django documentation [1], this is only effective when django.contrib.sessions.backends.cache is used as SESSION_ENGINE. I think it is better to switch the default SESSION_ENGINE to django.contrib.sessions.backends.cache. [1] https://docs.djangoproject.com/en/1.11/topics/http/sessions /#configuring-the-session-engine To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1736021/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
