mahara-contributors team mailing list archive

[Mahara Bot <890929@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://reviews.mahara.org/958
Committed: http://gitorious.org/mahara/mahara/commit/abda43b5dbbc9a4051f3a6f48606f62036082289
Submitter: Francois Marier (francois@xxxxxxxxxxxxxxx)
Branch:    master

commit abda43b5dbbc9a4051f3a6f48606f62036082289
Author: Richard Mansfield <richard.mansfield@xxxxxxxxxxxxxxx>
Date:   Thu Dec 22 15:03:05 2011 +1300

    Remove unused inactive check from login code (bug #890929)
    
    This code was never run because the $oldlastlogin variable was
    hardcoded to 0.  The code can be removed altogether, and instead rely
    on cron to set expiry dates on inactive users.
    
    Change-Id: I9883a7720960f2337edf060197346cd17f0193c5
    Signed-off-by: Richard Mansfield <richard.mansfield@xxxxxxxxxxxxxxx>

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
https://bugs.launchpad.net/bugs/890929

Title:
  When a user is expired due to inactivity, they can still log in

Status in Mahara ePortfolio:
  In Progress

Bug description:
  In the cronjob auth_handle_account_expiries, users that haven't logged
  in since the config option defaultaccountinactiveexpire get
  deactivated. This sets the active flag in the usr table.

  One would think that being inactive would mean that the user could no
  longer login, but they still can. Especially because the email sent
  out before you become inactive is as follows:

  "Dear Admin User (admin),

  Your account on Mahara will become inactive within 7 days.

  Once inactive, you will not be able to log in until an administrator
  re-enables your account.

  You can prevent your account from becoming inactive by logging in.

  Regards, Mahara Site Administrator

  Please do not reply to this message.
  "

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/890929/+subscriptions