0f51b58f75
The enrollmentStatusHash cookie value was created in commitf0030334as an optimization, in order to determine whether the marketing site needs to refresh the list of a student's enrolled courses with a call to the LMS. To ensure that this value was kept up to date, commitd7a7bcc1reset the user's cookies every time they go to the learner dashboard page (which used to be the next page loaded after you enrolled in a course). This didn't just reset the enrollmentStatusHash though -- it recalculated all the cookie values, as if you had just logged in. A number of things have changed since then: 1. Enrolling in a course now goes to that course's info/navigation page, rather than going to the student dashboard. 2. It doesn't appear that the value of enrollmentStatusHash is actually being examined anywhere -- it's set in a cookie on the LMS and read/written by the edX marketing front end code, but the value is never looked at to make any decisions. 3. The introduction of add_email_marketing_cookies (which triggers off of the CREATE_LOGON_COOKIE signal) has made cookie resets far more expensive, as there is a blocking call to Sailthru if you have that enabled in EmailMarketingConfiguration (which edx.org does). This can add over two seconds to the server processing time for the student dashboard at certain times of day. Given this, I'm removing both the call to resetting the cookie on the student dashboard page, as well as setting the value for enrollmentStatusHash.
Status: Maintenance Responsibilities ================ The ``user_authn`` app contains user authentication related features such as login and registration. Direction: Extract ================== Ideally this would be in its own service, but at this point, LMS is the home of all authentication related features. At this time, these features are still plugged into Studio. Future clean-up in Studio is intended to make this an LMS only feature. Glossary ======== More Documentation ==================