1. 15 May, 2015 2 commits
  2. 17 Apr, 2015 3 commits
  3. 25 Mar, 2015 1 commit
    • Login/Registration page can skip track selection. · 735b4009
      Add querystring param "course_mode" to the login/registration
      page so the user can skip track selection.
      
      This supports upcoming changes to the course details page
      that allow the user to choose the track when clicking
      "enroll", which will replace the functionality of the track
      selection page.
      Will Daly committed
  4. 17 Mar, 2015 2 commits
  5. 13 Mar, 2015 1 commit
  6. 26 Feb, 2015 1 commit
  7. 23 Feb, 2015 2 commits
  8. 11 Feb, 2015 1 commit
  9. 04 Feb, 2015 1 commit
    • Better support specifying of modulestore configuration in test cases · b353ed2e
      The existing pattern of using `override_settings(MODULESTORE=...)` prevented
      us from having more than one layer of subclassing in modulestore tests.
      
      In a structure like:
      
          @override_settings(MODULESTORE=store_a)
          class BaseTestCase(ModuleStoreTestCase):
              def setUp(self):
                  # use store
      
          @override_settings(MODULESTORE=store_b)
          class ChildTestCase(BaseTestCase):
              def setUp(self):
                  # use store
      
      In this case, the store actions performed in `BaseTestCase` on behalf of
      `ChildTestCase` would still use `store_a`, even though the `ChildTestCase`
      had specified to use `store_b`. This is because the `override_settings`
      decorator would be the innermost wrapper around the `BaseTestCase.setUp` method,
      no matter what `ChildTestCase` does.
      
      To remedy this, we move the call to `override_settings` into the
      `ModuleStoreTestCase.setUp` method, and use a cleanup to remove the override.
      Subclasses can just defined the `MODULESTORE` class attribute to specify which
      modulestore to use _for the entire `setUp` chain_.
      
      [PLAT-419]
      Calen Pennington committed
  10. 30 Jan, 2015 1 commit
    • Make logistration generally available if feature flag is active · a8bed5ce
      Makes logistration available at /login and /register as well as /accounts/login/ and /accounts/register/. In addition:
      
      - Adds support for redirect URLs in third party auth for combined login/registration page
      - Adds support for external auth on the combined login/registration page
      - Removes old login and registration acceptance tests
      - Adds deprecation warnings to old login and register views
      - Moves third party auth util to student_account
      - Adds exception for microsites (theming)
      Renzo Lucioni committed
  11. 19 Jan, 2015 1 commit
  12. 16 Jan, 2015 1 commit
  13. 09 Jan, 2015 1 commit
  14. 08 Dec, 2014 1 commit
  15. 05 Dec, 2014 2 commits
  16. 04 Dec, 2014 1 commit
  17. 12 Nov, 2014 2 commits
  18. 10 Nov, 2014 1 commit
  19. 07 Nov, 2014 1 commit
  20. 04 Nov, 2014 1 commit
  21. 30 Oct, 2014 1 commit
  22. 28 Oct, 2014 1 commit
  23. 22 Oct, 2014 1 commit
    • Integrate third party auth into the combined login/registration page. · 9e9dec1d
      Change third party auth login failure code to a 401, to detect authentication
      success with no linked account.
      
      If already authenticated, redirect immediately to the dashboard.
      
      Use "Location" header correctly for 302 redirects from student views.
      
      Add utility functions for simulating a running third-party auth pipeline.
      
      Add a utility function for checking whether third party auth is enabled.
      
      Respect default values sent by the server
      Will Daly committed
  24. 21 Oct, 2014 1 commit
  25. 20 Oct, 2014 1 commit
  26. 18 Oct, 2014 1 commit
  27. 16 Oct, 2014 1 commit
  28. 08 Oct, 2014 1 commit
  29. 01 Oct, 2014 1 commit
  30. 25 Sep, 2014 2 commits