Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Separate CMS Session from the Application Session #32

Open
sandio opened this issue Jan 12, 2015 · 2 comments
Open

Separate CMS Session from the Application Session #32

sandio opened this issue Jan 12, 2015 · 2 comments
Assignees
@pnikolov
Labels
low priority proposal security
Milestone
next

Comments

@sandio
Copy link
Contributor

sandio commented Jan 12, 2015

Usage of different session ids for the different application contexts.
@sandio sandio added this to the next milestone Jan 12, 2015
@pnikolov
Copy link
Member

To clarify, each one of the application modes (e.g. app/cms/api) should have its own Session identifier. This will separate the session variable storage, each Core\Session() instance will work in a sandbox for the current requested mode.

@pnikolov
Copy link
Member

Is this still required? Such feature causes poor UX and a lot of wired behavior e.g:

  • Having CMS session and trying to login in a different mode.

    @kalins @kmotsov what is the best practice in this case?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pnikolov pnikolov

Labels
low priority proposal security
Projects
None yet
Milestone
next
Development

No branches or pull requests
2 participants
@pnikolov @sandio