Horizon sessions do not properly observe SESSION_TIMEOUT

Bug #1632181 reported by chenyujie
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
django-openstack-auth
Expired
Undecided
Unassigned

Bug Description

Refer to Bug-fix #1562452:
-------------
This calculation uses the 'token_life' var which is a
datetime.timedelta object. timedelta.seconds gets us just the
'seconds' component of the object, truncating away any days, hours,
or weeks that might be included in the object.

What we want here is the total time in seconds, which is
total_seconds().
-------------
It is fixed in master branch and released in 2.3.0, but mitaka branch still have the same problem.

When keystone token lifetime larger than 1 day, such as 5 days, the problem would appear frequently and nothing can be done on horizon because login is required on almost every action.

Tags: session
Revision history for this message
chenyujie (gzyjchen) wrote :
information type: Private Security → Public
chenyujie (gzyjchen)
description: updated
Revision history for this message
David Lyle (david-lyle) wrote :

would require backport to mitaka stable branch, is the severe enough to warrant the backport?

Changed in django-openstack-auth:
status: New → Confirmed
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for django-openstack-auth because there has been no activity for 60 days.]

Changed in django-openstack-auth:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.