mahara-contributors team mailing list archive

[Hugh Davenport <890929@xxxxxxxxxxxxxxxxxx>]

I think it had something funny with the cronjob running it needed time
to rethink it

I would say it was after the 7 days, I actually set the
defaultaccountinactiveexpire setting to something very low (so email got
sent but wasn't actually an extra 7 days iirc). But I had to force the
cronjob to run twice, so that it set the active flag to 0 in usr table.

Though we should probably wait the 7 days really, but yeh... I didn't
want to wait that long :D

UPDATE cron SET nextrun=NULL WHERE
callfunction='auth_handle_account_expiries'

-- 
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:
  Triaged

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