Project-Id-Version: Trac 0.12
Report-Msgid-Bugs-To: trac-dev@googlegroups.com
POT-Creation-Date: 2008-01-30 09:20+0100
PO-Revision-Date: 2010-07-19 23:05+0200
Last-Translator: Jeroen Ruigrok van der Werven <asmodai@in-nomine.org>
Language-Team: en_US <trac-dev@googlegroups.com>
Plural-Forms: nplurals=2; plural=(n != 1)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Generated-By: Babel 0.9.6

Warning: Can't synchronize with repository "(default)" (Unsupported version control system "git": Can't find an appropriate component, maybe the corresponding plugin was not enabled? ). Look in the Trac log for more information.

Ticket #60 (new improvement)

Opened 10 years ago

Last modified 9 years ago

SUDO for admin

Reported by: sebastian Owned by:
Priority: minor Milestone: 2.4
Component: unspecified Version:
Keywords: sudo user change Cc:

Description

It would be nice to have a sudo mode for the admin that the admin can change easly to another user to help or manage the ordinary user account.

This could be helpful if an ordinary user is not able to upload tons of media but the admin (who runs most probably the phTagr gallery and has a good internet connection). The admin receives the media via ordinary post (e.g. on a DVD) and upload the media for the user.

The sudo mode helps also to fixes detailed problems without bothering the user.

Change History

comment:1 Changed 9 years ago by remy

Suggestion: Use "real" and "effective" user id/name.

Make a difference between the "real" username (or id) and the "effective" username. The "real" username is always the username which was used during login. The "effective" username is the one which the user wants to use at the time. A normal user can not change his "effective" username, it is always the same as the "real" username.
An admin can change (in the admin interface) his "effective" username to another username (or id). While doing so, all actions are performed as if he was that other user(name): He will not see the admin "system" interface, he will only have the permissions of that other user, but there will be a link (somewhere) to revert back to his "real" username.

Login and logout is always performed on the "real" username. All other actions should be performed (queried/logged) for the "effective" username. One exception, changing back the "effective" username to his "real" username.

Note: See TracTickets for help on using tickets.