"Error: Bad token, please reauthenticate" going from diablo to essex
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Dashboard (Horizon) |
Fix Released
|
High
|
Gabriel Hurley |
Bug Description
It appears session objects corrupt when you move between releases of dashboard.
When I try to login to essex dash after upgrading from diablo I see: Error: Bad token, please reauthenticate
And similarly I see in diablo: Unauthorized at /dash/
Bad token, please reauthenticate (HTTP 401)
----
document.cookie is "csrftoken=
-----
Steps:
1) install diablo devstack
2) login to dashboard
3) upgrade horizon to essex
4) open new tab and go to your dash url - it will show you the login page
5) try to login
Expected:
Either it lets the old token work (and recognizes who I am) or lets me login again
Actual:
I cannot login as long as I have my cookie. Even after many days (maybe a week), the cookie still causes issues (if you don't delete the cookie manual the dashboard doesn't remove it and it doesn't appear to timeout.
If I create an incognito tab (eg, a tab without an existing cookie/session), I am able to login.
Changed in horizon: | |
status: | New → Confirmed |
importance: | Undecided → High |
assignee: | nobody → termie (termie) |
milestone: | none → essex-2 |
Changed in horizon: | |
assignee: | nobody → termie (termie) |
Changed in horizon: | |
status: | Fix Committed → Fix Released |
Changed in horizon: | |
milestone: | essex-2 → 2012.1 |
notice that:
* essex sees the existing session when logging in but doesn't redirect to /nova
* diablo recognizes the session exists and sends you to /dash
This is probably because of https:/ /bugs.launchpad .net/horizon/ +bug/893219