search

HughP / simal

Automatically exported from code.google.com/p/simal
0 stars 0 forks source link

Refactor access control to edit project features #383

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
The access control to the edit features on the project detail page are 
currently managed by passing around a variable indicating if the user is logged 
in. This is not the best way to handle authentication.

Components should be authorised or otherwise using SimalAuthorisationStrategy

This centralises all access control and means that we can reuse panels in 
multiple places without worrying about accidentally blocking/allowing access 
innapropriately.

It also allows the authorisation to be overridden to allow different strategies 
(or to have it set from a properties file)

Original issue reported on code.google.com by ross.gardler on 9 Feb 2011 at 11:38

GoogleCodeExporter commented 9 years ago 
This issue was updated by revision r2155.

make the majority of edit features of components display when the user is 
authenticated.

TODO
====

- make the decsription fields editable without the need to click the edit 
button.

Original comment by rgardler...@gmail.com on 10 Feb 2011 at 11:18