Reviewed:  https://reviews.mahara.org/7799
Committed: 
https://git.mahara.org/mahara/mahara/commit/b13178e7c737c7b10eb68570fd1adf533dfcb065
Submitter: Robert Lyon (robe...@catalyst.net.nz)
Branch:    16.10_STABLE

commit b13178e7c737c7b10eb68570fd1adf533dfcb065
Author: Ilya Tregubov <i...@catalyst-au.net>
Date:   Thu Jun 1 13:37:49 2017 +1000

Bug #1694342: clean password from event_log takes long time

behatnotneeded

Change-Id: Ic511e25066ebd84b80118e71f70c6f867a3564b4

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask 
on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1694342

Title:
  Eventlog update in upgrade taking hours to process

Status in Mahara:
  Fix Committed
Status in Mahara 16.10 series:
  Fix Committed
Status in Mahara 17.04 series:
  Fix Committed
Status in Mahara 17.10 series:
  Fix Committed

Bug description:
  OS: Linux
  DB: Postgres
  Mahara: 16.10.4
  Browser: N/A

  With the latest security release for 16.10.4, the upgrade to clean the
  eventlog of sensitive data can take hours to process.

  We have over 56K records for the 'createuser' event. Most of them are
  LDAP accounts so the data looks like this:

  
  
"{"username":"abc","authinstance":"3","firstname":"first","lastname":"last","password":"","email":"myem...@nowhere.com","studentid":"1234","ctime":"2016-07-05
 11:29:21","urlid":"1234","quota":"524288000","id":85}"

  The upgrade updates these records to remove the '"password":""' data.

  I'll try to improve on this.

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

_______________________________________________
Mailing list: https://launchpad.net/~mahara-contributors
Post to     : mahara-contributors@lists.launchpad.net
Unsubscribe : https://launchpad.net/~mahara-contributors
More help   : https://help.launchpad.net/ListHelp

Reply via email to