Use request path to identify current project

Registered by Sahid Orentino

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

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
Sahid Orentino
Direction:
Needs approval
Assignee:
None
Definition:
Obsolete
Series goal:
None
Implementation:
Unknown
Milestone target:
None
Completed by
David Lyle

Related branches

Sprints

Whiteboard

[david-lyle | 2016-06-15] I see the potential value in such a change. My fear is that this is very invasive has a likely hood of regressions. Additionally, since this blueprint is 3 years old and untouched, I'm going to mark it obsolete. If someone wants to try this again, feel free.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.