Bug 1042067

Summary: [RFE][horizon]: Use request path to identify current project
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: RFEsAssignee: RHOS Maint <rhos-maint>
Status: CLOSED UPSTREAM QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: markmc, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/horizon/+spec/use-request-path-to-identify-current-project
Whiteboard: upstream_milestone_none upstream_status_unknown upstream_definition_obsolete
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-19 17:04:34 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

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