yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #49317
[Bug 1528967] Re: Horizon doesn't create new scoped token when user role is removed
*** This bug is a duplicate of bug 1252341 ***
https://bugs.launchpad.net/bugs/1252341
** This bug has been marked a duplicate of bug 1252341
Horizon crashes when removing logged user from project
--
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/1528967
Title:
Horizon doesn't create new scoped token when user role is removed
Status in OpenStack Dashboard (Horizon):
Confirmed
Bug description:
When a user logs into Horizon an unscoped token is created using which
a scoped token is obtained. I am logged into Horizon and remove myself
from a project which is not the current active project. This results
in all my scoped tokens getting invalidated. I have some API calls in
the middleware that require authorization which fail because the token
is invalid. Horizon will throw an Unauthorized error (see attachment)
and the only way to recover from this is to clear cookies, logout and
log back in again.
Horizon should immediately obtain a new scoped token if previous token
is invalidated. Alternatively, keystone should not invalidate all
tokens (for all projects) when user is removed from one project.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1528967/+subscriptions
References