-
Type: Sub-task
-
Status: Closed (View Workflow)
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: 0.16
-
Fix Version/s: 0.17
-
Labels:None
-
Environment:
deploy.jtalks.org/jcommune
As for now all Spring Security exceptions result "error 500" error page.
That's not convenient, cause we need a clear indication.
An attempt to access object we have insufficient privilegies for access to should result in a different error page with the appropriate caption.
To model this situation you may try to access another user's PM by substituting id in URL.