Kolibri should explicitly set cookie name #3921
Description
Observed behavior
When running Kolibri and Studio at the same time in the same browser, Kolibri will immediately sign the user out and require them to sign in again. This process will repeat for as long as both apps are running.
This happens because Kolibri and Studio both currently use the Django default cookie name, 'sessionid'. This causes Kolibri and Studio to set each other's sessionid after various actions.
Expected behavior
When you sign in, you stay signed in, Studio or not. :)
User-facing consequences
This is primarily an internal developer issue, though it could happen on devices that deploy other local services in addition to Kolibri that are using Django and keep the default cookie name.
Steps to reproduce
- Start Studio and sign in
- Start Kolibri and sign in
- Return to Kolibri and try to perform an action, like importing content
Result: It says you are signed out and asks you to sign in again. Once you sign in again, this process will repeat.
Context
- Latest Kolibri from develop branch as of 6-28-18
- Latest Studio from develop branch as of 6-28-18
- OS X 10.13 (High Sierra)
- Any browser, tested with Safari, Chrome, Chromium, and FIrefox