Horizon sessions do not properly observe SESSION_TIMEOUT

[Andrew Bogott]

The default value of SESSION_TIMEOUT in horizon is 1800, which works properly. Increasing that number works to a point, but timeout values are arbitrarily capped at 8639.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/298002

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/298002
Committed: https://git.openstack.org/cgit/openstack/django_openstack_auth/commit/?id=d7a2dce59d95979fb3d4ae5cdac9fd063c09d88d
Submitter: Jenkins
Branch: master

commit d7a2dce59d95979fb3d4ae5cdac9fd063c09d88d
Author: andrewbogott <email address hidden>
Date: Wed Mar 16 18:15:13 2016 -0500

    When calculating session_time, use the actual token life

    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().

    Closes-Bug: #1562452
    Change-Id: I6a947abb891e1d34e1cf3aea53b345e0a804bacf

[Thierry Carrez (ttx)]

This issue was fixed in the openstack/django_openstack_auth 2.3.0 release.