Details
-
Bug
-
Resolution: Fixed
-
Major
-
3.0 Beta 1
-
None
-
Windows XP, Magnolia 3.0 RC1 build 3345, Jetty 6-Beta17
Description
- Login as 'superuser'
- Create a Group A
- Create a User B
- Assign Group A to User B (wouldn't the other way around be more logical?)
- Define a Role with Read only for the whole WEBSITE repository
- Assign Role to Group A (which should be inherited by User A, right?)
- Log out
- Log in as User B
---> You will get a 403 (Forbidden)
Now comes the strange part: - Close the browser
- Open a new browser
- Login as 'superuser'
---> You will get a 403 (Forbidden) again!!
After restarting Jetty I can login again as 'superuser'
I have choosen "Major" priority, but for the project we are doing it actually is a "Blocker". So if you could provide a workaround, that would be truely apreciated!
Checklists
Acceptance criteria