[Mahara-contributors] [Bug 1027574] Re: Improve logging of what admins do while masqueraded

2013-08-19 Thread Kristina Hoeppner
A new wishlist item bug #1213875 has been opened to capture any further
work so as to keep better track of things.

** No longer affects: mahara/1.8

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contrib members
https://bugs.launchpad.net/bugs/1027574

Title:
  Improve logging of what admins do while masqueraded

Status in Mahara ePortfolio:
  Fix Released

Bug description:
  Loginas is a great feature for admins to check permissiosn as a
  special user.  In several environments its seen very critical because
  admins can change anything as the user who is logged in.  Its not
  documented that the  changes are not done by the user and the admin
  did them.

  It makes ot of sense to document that an admin changed anything in the name 
of the user.  I've two ideas how to do this:
  1. mark all changs in the interface as changed by admin [name of admin] 
[date and time] of change.
  2. write changes done by admin when logged in as a user into a seperate 
database and create a report page that shows this database information sortable 
by date, user and admin who made changes. This  report should include: 
  - date and time of login as
  - date and time when login as was finished
  - did admin make changes in the name of the user?
  - who logged in as other user (name of admin)
  - login as which user [name of user]
  - where was change done [URL]
  - old entry from user
  - changed and stored new entry by admin

  The report should only by accessible for site admins.
  The report should be downloadable.
  If files were added or deleted or renamed the information should be included 
but notthe file istself.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1027574/+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


[Mahara-contributors] [Bug 1027574] Re: Improve logging of what admins do while masqueraded

2013-04-18 Thread Aaron Wells
** Changed in: mahara
   Status: Fix Committed = Fix Released

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contrib members
https://bugs.launchpad.net/bugs/1027574

Title:
  Improve logging of what admins do while masqueraded

Status in Mahara ePortfolio:
  Fix Released
Status in Mahara 1.8 series:
  Confirmed

Bug description:
  Loginas is a great feature for admins to check permissiosn as a
  special user.  In several environments its seen very critical because
  admins can change anything as the user who is logged in.  Its not
  documented that the  changes are not done by the user and the admin
  did them.

  It makes ot of sense to document that an admin changed anything in the name 
of the user.  I've two ideas how to do this:
  1. mark all changs in the interface as changed by admin [name of admin] 
[date and time] of change.
  2. write changes done by admin when logged in as a user into a seperate 
database and create a report page that shows this database information sortable 
by date, user and admin who made changes. This  report should include: 
  - date and time of login as
  - date and time when login as was finished
  - did admin make changes in the name of the user?
  - who logged in as other user (name of admin)
  - login as which user [name of user]
  - where was change done [URL]
  - old entry from user
  - changed and stored new entry by admin

  The report should only by accessible for site admins.
  The report should be downloadable.
  If files were added or deleted or renamed the information should be included 
but notthe file istself.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1027574/+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


[Mahara-contributors] [Bug 1027574] Re: Improve logging of what admins do while masqueraded

2013-02-19 Thread Melissa Draper
** Changed in: mahara
   Status: Triaged = Fix Committed

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

Title:
  Improve logging of what admins do while masqueraded

Status in Mahara ePortfolio:
  Fix Committed
Status in Mahara 1.8 series:
  New

Bug description:
  Loginas is a great feature for admins to check permissiosn as a
  special user.  In several environments its seen very critical because
  admins can change anything as the user who is logged in.  Its not
  documented that the  changes are not done by the user and the admin
  did them.

  It makes ot of sense to document that an admin changed anything in the name 
of the user.  I've two ideas how to do this:
  1. mark all changs in the interface as changed by admin [name of admin] 
[date and time] of change.
  2. write changes done by admin when logged in as a user into a seperate 
database and create a report page that shows this database information sortable 
by date, user and admin who made changes. This  report should include: 
  - date and time of login as
  - date and time when login as was finished
  - did admin make changes in the name of the user?
  - who logged in as other user (name of admin)
  - login as which user [name of user]
  - where was change done [URL]
  - old entry from user
  - changed and stored new entry by admin

  The report should only by accessible for site admins.
  The report should be downloadable.
  If files were added or deleted or renamed the information should be included 
but notthe file istself.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1027574/+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


[Mahara-contributors] [Bug 1027574] Re: Improve logging of what admins do while masqueraded

2013-02-18 Thread Melissa Draper
** Also affects: mahara/1.8
   Importance: Undecided
   Status: New

** Changed in: mahara
 Assignee: (unassigned) = Jiri Baum (Catalyst) (jiri-catalyst)

** Changed in: mahara
Milestone: None = 1.7.0

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

Title:
  Improve logging of what admins do while masqueraded

Status in Mahara ePortfolio:
  Triaged
Status in Mahara 1.8 series:
  New

Bug description:
  Loginas is a great feature for admins to check permissiosn as a
  special user.  In several environments its seen very critical because
  admins can change anything as the user who is logged in.  Its not
  documented that the  changes are not done by the user and the admin
  did them.

  It makes ot of sense to document that an admin changed anything in the name 
of the user.  I've two ideas how to do this:
  1. mark all changs in the interface as changed by admin [name of admin] 
[date and time] of change.
  2. write changes done by admin when logged in as a user into a seperate 
database and create a report page that shows this database information sortable 
by date, user and admin who made changes. This  report should include: 
  - date and time of login as
  - date and time when login as was finished
  - did admin make changes in the name of the user?
  - who logged in as other user (name of admin)
  - login as which user [name of user]
  - where was change done [URL]
  - old entry from user
  - changed and stored new entry by admin

  The report should only by accessible for site admins.
  The report should be downloadable.
  If files were added or deleted or renamed the information should be included 
but notthe file istself.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1027574/+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


[Mahara-contributors] [Bug 1027574] Re: Improve logging of what admins do while masqueraded

2013-01-07 Thread Kristina Hoeppner
** Tags added: nominatedfeature

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

Title:
  Improve logging of what admins do while masqueraded

Status in Mahara ePortfolio:
  Triaged

Bug description:
  Loginas is a great feature for admins to check permissiosn as a
  special user.  In several environments its seen very critical because
  admins can change anything as the user who is logged in.  Its not
  documented that the  changes are not done by the user and the admin
  did them.

  It makes ot of sense to document that an admin changed anything in the name 
of the user.  I've two ideas how to do this:
  1. mark all changs in the interface as changed by admin [name of admin] 
[date and time] of change.
  2. write changes done by admin when logged in as a user into a seperate 
database and create a report page that shows this database information sortable 
by date, user and admin who made changes. This  report should include: 
  - date and time of login as
  - date and time when login as was finished
  - did admin make changes in the name of the user?
  - who logged in as other user (name of admin)
  - login as which user [name of user]
  - where was change done [URL]
  - old entry from user
  - changed and stored new entry by admin

  The report should only by accessible for site admins.
  The report should be downloadable.
  If files were added or deleted or renamed the information should be included 
but notthe file istself.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1027574/+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


[Mahara-contributors] [Bug 1027574] Re: Improve logging of what admins do while masqueraded

2013-01-03 Thread Kristina Hoeppner
For testing:

There is a site option under User settings where the reason for
masquerading can be turned on.

Logs can also be turned on in a new Site option Logging settings.

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

Title:
  Improve logging of what admins do while masqueraded

Status in Mahara ePortfolio:
  Triaged

Bug description:
  Loginas is a great feature for admins to check permissiosn as a
  special user.  In several environments its seen very critical because
  admins can change anything as the user who is logged in.  Its not
  documented that the  changes are not done by the user and the admin
  did them.

  It makes ot of sense to document that an admin changed anything in the name 
of the user.  I've two ideas how to do this:
  1. mark all changs in the interface as changed by admin [name of admin] 
[date and time] of change.
  2. write changes done by admin when logged in as a user into a seperate 
database and create a report page that shows this database information sortable 
by date, user and admin who made changes. This  report should include: 
  - date and time of login as
  - date and time when login as was finished
  - did admin make changes in the name of the user?
  - who logged in as other user (name of admin)
  - login as which user [name of user]
  - where was change done [URL]
  - old entry from user
  - changed and stored new entry by admin

  The report should only by accessible for site admins.
  The report should be downloadable.
  If files were added or deleted or renamed the information should be included 
but notthe file istself.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1027574/+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


[Mahara-contributors] [Bug 1027574] Re: Improve logging of what admins do while masqueraded

2013-01-03 Thread Kristina Hoeppner
Hi Jiri,

Thanks for the development. Looks already good. :-)

Did you already work on the table in the admin area (in the User reports
area) to display to the admins when another admin had logged in and for
what reason? I see that you have Logging information that is to be
written to the database, but that must be something different.

Thanks
Kristina

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

Title:
  Improve logging of what admins do while masqueraded

Status in Mahara ePortfolio:
  Triaged

Bug description:
  Loginas is a great feature for admins to check permissiosn as a
  special user.  In several environments its seen very critical because
  admins can change anything as the user who is logged in.  Its not
  documented that the  changes are not done by the user and the admin
  did them.

  It makes ot of sense to document that an admin changed anything in the name 
of the user.  I've two ideas how to do this:
  1. mark all changs in the interface as changed by admin [name of admin] 
[date and time] of change.
  2. write changes done by admin when logged in as a user into a seperate 
database and create a report page that shows this database information sortable 
by date, user and admin who made changes. This  report should include: 
  - date and time of login as
  - date and time when login as was finished
  - did admin make changes in the name of the user?
  - who logged in as other user (name of admin)
  - login as which user [name of user]
  - where was change done [URL]
  - old entry from user
  - changed and stored new entry by admin

  The report should only by accessible for site admins.
  The report should be downloadable.
  If files were added or deleted or renamed the information should be included 
but notthe file istself.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1027574/+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


[Mahara-contributors] [Bug 1027574] Re: Improve logging of what admins do while masqueraded

2013-01-03 Thread Jiri Baum (Catalyst)
There is only the one report for now, which is in the User reports
section.

Go to Admin - Users, select users and/or admins of interest, Get
reports, Masquerading sessions tab.

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

Title:
  Improve logging of what admins do while masqueraded

Status in Mahara ePortfolio:
  Triaged

Bug description:
  Loginas is a great feature for admins to check permissiosn as a
  special user.  In several environments its seen very critical because
  admins can change anything as the user who is logged in.  Its not
  documented that the  changes are not done by the user and the admin
  did them.

  It makes ot of sense to document that an admin changed anything in the name 
of the user.  I've two ideas how to do this:
  1. mark all changs in the interface as changed by admin [name of admin] 
[date and time] of change.
  2. write changes done by admin when logged in as a user into a seperate 
database and create a report page that shows this database information sortable 
by date, user and admin who made changes. This  report should include: 
  - date and time of login as
  - date and time when login as was finished
  - did admin make changes in the name of the user?
  - who logged in as other user (name of admin)
  - login as which user [name of user]
  - where was change done [URL]
  - old entry from user
  - changed and stored new entry by admin

  The report should only by accessible for site admins.
  The report should be downloadable.
  If files were added or deleted or renamed the information should be included 
but notthe file istself.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1027574/+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


[Mahara-contributors] [Bug 1027574] Re: Improve logging of what admins do while masqueraded

2013-01-03 Thread Jiri Baum (Catalyst)
PS - the logging information does include events for beginning of
masquerading session (patch 1940 adds this event type), so the
masquerading session report just summarises those events from the log.

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

Title:
  Improve logging of what admins do while masqueraded

Status in Mahara ePortfolio:
  Triaged

Bug description:
  Loginas is a great feature for admins to check permissiosn as a
  special user.  In several environments its seen very critical because
  admins can change anything as the user who is logged in.  Its not
  documented that the  changes are not done by the user and the admin
  did them.

  It makes ot of sense to document that an admin changed anything in the name 
of the user.  I've two ideas how to do this:
  1. mark all changs in the interface as changed by admin [name of admin] 
[date and time] of change.
  2. write changes done by admin when logged in as a user into a seperate 
database and create a report page that shows this database information sortable 
by date, user and admin who made changes. This  report should include: 
  - date and time of login as
  - date and time when login as was finished
  - did admin make changes in the name of the user?
  - who logged in as other user (name of admin)
  - login as which user [name of user]
  - where was change done [URL]
  - old entry from user
  - changed and stored new entry by admin

  The report should only by accessible for site admins.
  The report should be downloadable.
  If files were added or deleted or renamed the information should be included 
but notthe file istself.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1027574/+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


[Mahara-contributors] [Bug 1027574] Re: Improve logging of what admins do while masqueraded

2013-01-02 Thread Jiri Baum (Catalyst)
A partial implementation of this is now up on gerrit,
https://reviews.mahara.org/1940
https://reviews.mahara.org/1941
https://reviews.mahara.org/1942

Included:
+ Log everything admins do while masquerading (and optionally everything 
everyone does) to the database.
+ Ask the admin to provide a reason for masquerading.
+ Report of who, when and why masqueraded (start of masquerading session, 
including both user IDs).

Not included:
- Report of what admins did while masquerading.

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

Title:
  Improve logging of what admins do while masqueraded

Status in Mahara ePortfolio:
  Triaged

Bug description:
  Loginas is a great feature for admins to check permissiosn as a
  special user.  In several environments its seen very critical because
  admins can change anything as the user who is logged in.  Its not
  documented that the  changes are not done by the user and the admin
  did them.

  It makes ot of sense to document that an admin changed anything in the name 
of the user.  I've two ideas how to do this:
  1. mark all changs in the interface as changed by admin [name of admin] 
[date and time] of change.
  2. write changes done by admin when logged in as a user into a seperate 
database and create a report page that shows this database information sortable 
by date, user and admin who made changes. This  report should include: 
  - date and time of login as
  - date and time when login as was finished
  - did admin make changes in the name of the user?
  - who logged in as other user (name of admin)
  - login as which user [name of user]
  - where was change done [URL]
  - old entry from user
  - changed and stored new entry by admin

  The report should only by accessible for site admins.
  The report should be downloadable.
  If files were added or deleted or renamed the information should be included 
but notthe file istself.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1027574/+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


[Mahara-contributors] [Bug 1027574] Re: Improve logging of what admins do while masqueraded

2012-10-17 Thread Hugh Davenport
Just a note to who picks this up, the lastaccess field is updated for a
user even when being masqueraded by an admin. This should not happen,
instead it should update the lastaccess field of the admin user.

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

Title:
  Improve logging of what admins do while masqueraded

Status in Mahara ePortfolio:
  Triaged

Bug description:
  Loginas is a great feature for admins to check permissiosn as a
  special user.  In several environments its seen very critical because
  admins can change anything as the user who is logged in.  Its not
  documented that the  changes are not done by the user and the admin
  did them.

  It makes ot of sense to document that an admin changed anything in the name 
of the user.  I've two ideas how to do this:
  1. mark all changs in the interface as changed by admin [name of admin] 
[date and time] of change.
  2. write changes done by admin when logged in as a user into a seperate 
database and create a report page that shows this database information sortable 
by date, user and admin who made changes. This  report should include: 
  - date and time of login as
  - date and time when login as was finished
  - did admin make changes in the name of the user?
  - who logged in as other user (name of admin)
  - login as which user [name of user]
  - where was change done [URL]
  - old entry from user
  - changed and stored new entry by admin

  The report should only by accessible for site admins.
  The report should be downloadable.
  If files were added or deleted or renamed the information should be included 
but notthe file istself.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1027574/+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


[Mahara-contributors] [Bug 1027574] Re: Improve logging of what admins do while masqueraded

2012-07-27 Thread Kristina Hoeppner
Dirk has already put a wishlist item up for something similar at
https://bugs.launchpad.net/mahara/+bug/900983 There he wants to let
users know when an admin was in the account.

I would add to your proposal that institution admins should be able to
see a report for the members they are managing and the site admins can
see everything.

With the access reports in 1.5 we can reduce some of the necessity to
login as another user, but it's not entirely avoidable.

What would you say to also display to a user when an admin had accessed
the account?

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

Title:
  Improve logging of what admins do while masqueraded

Status in Mahara ePortfolio:
  Triaged

Bug description:
  Loginas is a great feature for admins to check permissiosn as a
  special user.  In several environments its seen very critical because
  admins can change anything as the user who is logged in.  Its not
  documented that the  changes are not done by the user and the admin
  did them.

  It makes ot of sense to document that an admin changed anything in the name 
of the user.  I've two ideas how to do this:
  1. mark all changs in the interface as changed by admin [name of admin] 
[date and time] of change.
  2. write changes done by admin when logged in as a user into a seperate 
database and create a report page that shows this database information sortable 
by date, user and admin who made changes. This  report should include: 
  - date and time of login as
  - date and time when login as was finished
  - did admin make changes in the name of the user?
  - who logged in as other user (name of admin)
  - login as which user [name of user]
  - where was change done [URL]
  - old entry from user
  - changed and stored new entry by admin

  The report should only by accessible for site admins.
  The report should be downloadable.
  If files were added or deleted or renamed the information should be included 
but notthe file istself.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1027574/+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


[Mahara-contributors] [Bug 1027574] Re: Improve logging of what admins do while masqueraded

2012-07-25 Thread Hugh Davenport
** Summary changed:

- loginas
+ Improve logging of what admins do while masqueraded

** Changed in: mahara
   Status: New = Triaged

** Changed in: mahara
   Importance: Undecided = Wishlist

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

Title:
  Improve logging of what admins do while masqueraded

Status in Mahara ePortfolio:
  Triaged

Bug description:
  Loginas is a great feature for admins to check permissiosn as a
  special user.  In several environments its seen very critical because
  admins can change anything as the user who is logged in.  Its not
  documented that the  changes are not done by the user and the admin
  did them.

  It makes ot of sense to document that an admin changed anything in the name 
of the user.  I've two ideas how to do this:
  1. mark all changs in the interface as changed by admin [name of admin] 
[date and time] of change.
  2. write changes done by admin when logged in as a user into a seperate 
database and create a report page that shows this database information sortable 
by date, user and admin who made changes. This  report should include: 
  - date and time of login as
  - date and time when login as was finished
  - did admin make changes in the name of the user?
  - who logged in as other user (name of admin)
  - login as which user [name of user]
  - where was change done [URL]
  - old entry from user
  - changed and stored new entry by admin

  The report should only by accessible for site admins.
  The report should be downloadable.
  If files were added or deleted or renamed the information should be included 
but notthe file istself.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1027574/+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