 | New Concept
|
Information
This is documenting the ideas and possible ways to extend the become user (SU) tool to handle more use cases. It currently allows an admin to become any user but that is all it allows. We would like to extend it to allow users with the right permission to become a fake user with any role they choose (configurable somehow). This page summarizes the thread which discussed possible options.
- Defining the issues and capturing the requirements - Become User Problem Space (feel free to add yours to this page)
Become User Extension
- Goals
- Add in functionality to expose the tool to users besides the super admin
- Allow users to become a "fake" user with a certain role
- Provide a way to link the fake activity back to the real user
- Allow the user to revert back to the original account
- Ideas that seemed to be accepted
- Store the original user id in the current session
- Create a temporary fake user with similar access to the original but different roles
- Make sure it acts just like a student account would in most circumstances
- Limit access to switch users based on a permission
- Control what roles can be switched to based on configuration
- Log all activity so it can easily be tied back to the original user
- Questions
- What should happen when a user performs a write action as the "fake" user, does this stay? How is it tied back to the original user?
- JIRA Issue: http://bugs.sakaiproject.org/jira/browse/SAK-7924
Specific ideas for solutions and comments
(more info under the link)
