Posted on 28/10/2015 10:52:55
Hi Nicolai,
Yeah, that would do the trick. In fact I feel that's what most customer consider how the impersonation should work (given their comments). Can you suggest the best way to approach the issue?
Here's what I though so far
- Keep the impersonation backend features to get a list of users the logged in user can impersonate
- Overriding (somehow) the secondary login method to save the primary login user on session variable, log him out and log in the "new one"
- Overriding the logout method to check if there's was a primary login user and log him in
I see the issue with getting an accurate audit trail for both the impersonater and the impersonatee, but hopefully the client can live without it, unless you find a better way to do it.
The main thing is getting impersonation to work, as per the projects request "navigate and see the website as my client would".
Looking forward for your comments,
Nuno Aguiar