Bug 1042067 - [RFE][horizon]: Use request path to identify current project
Summary: [RFE][horizon]: Use request path to identify current project
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/hori...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 20:49 UTC by RHOS Integration
Modified: 2016-06-17 04:04 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-19 17:04:34 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description RHOS Integration 2013-12-12 20:49:03 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/horizon/+spec/use-request-path-to-identify-current-project.

Description:

Note:
  In this document I use project to refer to the also known name tenant.

The current implementation to switch between projects use a session stored in a cookie. This can create a strange behavior when we try to use more than two windows/tabs open with different projects in a same browser because the session is shared. (mismatch between projects).

I suggest to extract the project Id from the session to pass it to the request path and so avoiding this behavior.

About the implementation:
  + To follow the current path pattern, we can add a new rule to handle the project id by that way:
        https://example.org/project/{project_id}/ 

  + Switching between projects means using different tokens. The current implementation of sessions may need to keep track of tuples (project Id, token).



Specification URL (additional information):

None


Note You need to log in before you can comment on or make changes to this bug.