Lab caches object permissions, not realizing that user has new role [was #8125]
As a result of TG-463 resolved now, there can be the situation that a user has a new role activated in his session by a project leader. However, the Lab does store Object permissions and does not try to re-read them in such a case.
To reproduce (a bit complicated, sorry :-)
1. find (or make up) a project P where A is Manager and B is Observer with some resource R
2. Let A and B log in into two different Lab instances
3. B opens Navigator, browses to P, opens R
4. B modifies R but cannot save (error message, no permissions)
5. A gives B the Editor role
6. B now tries to save but the same error message still appears although she has Editor role now
Currently, B has to refresh the Navigator in order to invalidate the cache and to update R's permissions, which is not very nice, especially if she had closed the Navigator after opening R...
One solution for this case could be to do a retry once a write operation has failed. However, this is not generic as there could be other combinations of existing and added roles.