yahoo-eng-team team mailing list archive

[Yves-Gwenael Bourhis <yves-gwenael.bourhis@xxxxxxxxxxxxx>]

Public bug reported:

If both the keyston token and the session expired, the user is asked to log in twice.
This is because the session timestamp is written only if a user is logged authenticated.
When a user has timed out both in session and keystone token validity, the user is asked to log in, then the timestamp is checked, and the user loged out again and asked to log in a second time.

Steps to reproduce:
================
- set in /etc/kestone/keystone.conf under the [token] section::

    expiration=10

- set in openstack_dashboard/local/local_settings set::

    SESSION_TIMEOUT = 10

- wait for both session and token to timeout (> 10 seconds :-) )

You are asked to login twice in a row.

** Affects: horizon
     Importance: Undecided
     Assignee: Yves-Gwenael Bourhis (yves-gwenael-bourhis)
         Status: In Progress

** Changed in: horizon
     Assignee: (unassigned) => Yves-Gwenael Bourhis (yves-gwenael-bourhis)

** Changed in: horizon
       Status: New => In Progress

** Description changed:

  If both the keyston token and the session expired, the user is asked to log in twice.
  This is because the session timestamp is written only if a user is logged authenticated.
- When a user as timed out bith in session and keystone token validity, the user is asked to log in, then the timestamp is checked, and the user loged out again and asked to log in a second time.
+ When a user has timed out both in session and keystone token validity, the user is asked to log in, then the timestamp is checked, and the user loged out again and asked to log in a second time.
  
  Steps to reproduce:
  ================
  - set in /etc/kestone/keystone.conf under the [token] section::
  
-     expiration=10
+     expiration=10
  
  - set in openstack_dashboard/local/local_settings set::
  
-     SESSION_TIMEOUT = 10
+     SESSION_TIMEOUT = 10
  
  - wait for both session and token to timeout (> 10 seconds :-) )
  
  You are asked to login twice in a row.

-- 
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/1308918

Title:
  If both kystone token and session have timeed out, a user is invited
  to login twice in a row

Status in OpenStack Dashboard (Horizon):
  In Progress

Bug description:
  If both the keyston token and the session expired, the user is asked to log in twice.
  This is because the session timestamp is written only if a user is logged authenticated.
  When a user has timed out both in session and keystone token validity, the user is asked to log in, then the timestamp is checked, and the user loged out again and asked to log in a second time.

  Steps to reproduce:
  ================
  - set in /etc/kestone/keystone.conf under the [token] section::

      expiration=10

  - set in openstack_dashboard/local/local_settings set::

      SESSION_TIMEOUT = 10

  - wait for both session and token to timeout (> 10 seconds :-) )

  You are asked to login twice in a row.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1308918/+subscriptions