fe3d855986
This is intended to silence a rare false positive that seems to happen when someone logs in on a browser that already has an active session for another user. We believe there should be no further positives once this case is handled. - login and logout views annotate the response to indicate the session user should be changing between the request and response phases - safe-sessions middleware skips the verify-user check when this annotation is present Also: - Adds a test around existing behavior for unexpected user-changes - Remove logging control based on `is_from_log_out`. This reverts most of af9e26f/PR #11479 for two reasons: - The safe-sessions `_verify_user` code has since changed to check for `request.user.id == None` - A commit later in the PR changes the login and logout pages to signal that the user/session change is expected
Status: Active Development Responsibilities ================ The courseware djangoapp is responsible for presenting course content to learners. Glossary ======== More Documentation ================== `Architectural Decision Records <https://github.com/edx/edx-platform/tree/master/lms/djangoapps/courseware/docs/decisions>`_