1. 02 Sep, 2013 1 commit
    • Aaron Wells's avatar
      Changing PluginAuth API to specifically indicate whether Auth requires remote username · 20512fdb
      Aaron Wells authored
      Bug 1160093: This adds a few new methods to the Auth class, which represents an auth instance:
      
       - is_parent_authority(): Indicates whether this auth instance is a parent authority or not
       - get_parent_authority(): Gets the ID of this auth instance's parent authority
       - needs_remote_username(): Indicates whether this auth instance needs the user to have a
            remote username setting (in auth_remote_user table)
      
      I've also updated the SAML and XMLRPC auth types, which are the only ones that use remote username.
      And I've updated create_user() to automatically populate auth_remote_user() for auth
      instances that use it.
      
      Note that an auth instance of ANY type will need a remote username if it's the parent to another
      authority (the parent feature allows a user to log in via the parent or the child auth instance;
      so it's quite possible for the user to have different usernames in the two of them. Currently
      only XMLRPC uses the parent auth feature.)
      
      Lastly, also updated the documentation of LiveUser->create_user() to indicate that it only
      uses the $remoteauth parameter as a boolean (which was true even before my code changes).
      
      Change-Id: I39b1b74e68cdbc9c2632b886655caaaece1bd312
      20512fdb
  2. 15 Aug, 2013 1 commit
  3. 23 Jun, 2013 1 commit
    • Son Nguyen's avatar
      Email address in the 'Required profile fields' form must be validated · 032b155d
      Son Nguyen authored
      (bug #1045563)
      
      When an user complete the required profile field,
      1. Check if the email address has been taken
      2. Send a validation email to this address
      
      3. If an email has been sent, display the status message.
      
      When an user validate his/her email address
      4. if it is the primary email, update the email field of the table
      'usr' in DB
      
      Change-Id: Ie3f8268bee9890c7f568a399da4332bb5ab44447
      Signed-off-by: Robert Lyon's avatarRobert Lyon <robertl@catalyst.net.nz>
      032b155d
  4. 17 Jan, 2013 1 commit
  5. 16 Jan, 2013 1 commit
  6. 15 Jan, 2013 1 commit
    • Ali Kaye's avatar
      Bug #1097564 Include contact information · 731e8115
      Ali Kaye authored
      Modified mahara.php and lib.php so that when
       a user with an expired account tries to log in
      they are told 'Sorry, your account has expired.
      You can contact the site administrator to have
      the account reactivated,' with a link to the
      'Contact Us' page.
      
      Change-Id: I6b461d40e37a88ac513649a1d4a6d83c5d3711a4
      Signed-off-by: default avatarAli Kaye <alexandrakaye.student@wegc.school.nz>
      731e8115
  7. 19 Nov, 2012 1 commit
  8. 10 Sep, 2012 1 commit
  9. 06 Sep, 2012 1 commit
  10. 03 Sep, 2012 1 commit
  11. 29 Aug, 2012 1 commit
  12. 31 Jul, 2012 1 commit
  13. 30 Jul, 2012 1 commit
  14. 25 Jul, 2012 1 commit
  15. 12 Jul, 2012 1 commit
  16. 23 May, 2012 2 commits
  17. 18 May, 2012 1 commit
    • Richard Mansfield's avatar
      Add local hooks for registration and user initialisation (bug #1001064) · 5d737aa5
      Richard Mansfield authored
      Three new hooks are added:
      
      local_init_user() - called after $USER is initialised.  This is useful
      for changing the user's theme before $THEME is initialised.
      
      local_register_submit() - called when the registration form is
      successfully submitted, but before the submitted values are saved to
      usr_registration.  This is useful for remembering the properties or
      preferences of the logged-out user when the form was submitted.
      
      local_post_register() - called after a user has successfully been
      created and logged in during registration.  This is useful when
      properties of the user (which may have been saved to usr_registration
      by local_register_submit()) need to be transferred to the newly
      registered user.
      
      Change-Id: Ifcb19737bdcecb550185624f2fd78e541690a337
      Signed-off-by: default avatarRichard Mansfield <richard.mansfield@catalyst.net.nz>
      5d737aa5
  18. 15 May, 2012 1 commit
    • Hugh Davenport's avatar
      Add ability to register with a BrowserID (bug #986004) · a5a97f21
      Hugh Davenport authored
      When a user clicks on "BrowserID Login", one of three things will happen
      1- If they have an account, they will login
      2- If they don't but there is one authinstance with browserid is present
          AND it has weautocreateusers enabled, then they will get an account
          in that institution, and login
      3- If none of the above is true, they will get redirected to a register
          page, which follows same self registration pattern as the internal
          authentication with the "confirm email" step removed.
      
      Change-Id: Idde3166e0664bf2acdc1da32271125e91d43af9c
      Signed-off-by: default avatarHugh Davenport <hugh@catalyst.net.nz>
      a5a97f21
  19. 01 May, 2012 2 commits
  20. 30 Apr, 2012 1 commit
  21. 23 Feb, 2012 1 commit
  22. 17 Feb, 2012 1 commit
  23. 01 Feb, 2012 1 commit
  24. 16 Jan, 2012 1 commit
  25. 11 Jan, 2012 2 commits
  26. 10 Jan, 2012 4 commits
  27. 09 Jan, 2012 1 commit
  28. 21 Dec, 2011 2 commits
  29. 20 Dec, 2011 1 commit
  30. 16 Dec, 2011 4 commits