Silla.IO
Silla.IO copied to clipboard
Separate CMS Session from the Application Session
trafficstars
Usage of different session ids for the different application contexts.
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.
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?