yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #47764
[Bug 1555415] [NEW] Session timeout from AngularJS pages doesn't give user feedback
Public bug reported:
At the moment we have very high-level code in the config() of
framework.module.js which redirects the user to the login page if an API
action is unauthorised (session timeout). There's no visible feedback to
the user at this point though.
I think we need to move the addition of that handler to a run() so that
the horizon.framework.widgets.toast.service is available and we can
throw up a toast telling the user that they've been logged out. We can't
include it in the config() because at that time the toast service hasn't
been instantiated.
You can see this in action by loading up the swift UI and forcing a
session invalidation, then clicking on some action like viewing a
container contents.
** 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/1555415
Title:
Session timeout from AngularJS pages doesn't give user feedback
Status in OpenStack Dashboard (Horizon):
New
Bug description:
At the moment we have very high-level code in the config() of
framework.module.js which redirects the user to the login page if an
API action is unauthorised (session timeout). There's no visible
feedback to the user at this point though.
I think we need to move the addition of that handler to a run() so
that the horizon.framework.widgets.toast.service is available and we
can throw up a toast telling the user that they've been logged out. We
can't include it in the config() because at that time the toast
service hasn't been instantiated.
You can see this in action by loading up the swift UI and forcing a
session invalidation, then clicking on some action like viewing a
container contents.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1555415/+subscriptions
Follow ups