- Issue created by @daniel.pernold
When masquerading from admin to a user with a specific role, permissions get calculated differently then when logging in the user itself.
Step 1
* Login as admin
* Navigate to /admin/people
* Masquerade User with role A via button on the right
* No further masquerading to a user available (button not available), despite the permissions are set correctly for these roles.
Step 2
* Login as User with role A
* Navigate to /admin/people
* Same behaviour as in Step 1 (no furhter masquerading available - button does not exist)
Step 3
* Login as User with role A
* Cache Rebuild
* Navigate to /admin/people
* Masquerading available as button as configured
I'm not sure whether the disabled masquerading functionality is by design when one is already a masqueraded user, but the cache for this user never gets invalidated. So the masquerading functionality is broken for logged in users with a "wrong" cache being filled when an admin masqueraded to this user before.
Active
2.0
User interface