Review of security declarations for modules (especially adapters)
Bug #101399 reported by
Walco van Loon
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Silva |
Invalid
|
Low
|
Sylvain Viollon | ||
Bug Description
At the moment there is a myriad of ways and places to expose adapters and their
methods to ZPTs and Python scripts. A unified (centralized) approach to security
declarations would simplify future upgrade paths and make new development easier.
Revision history for this message
| Sylvain Viollon (thefunny) wrote | #1 |
| Changed in silva: | |
| assignee: | nobody → Sylvain Viollon (thefunny) |
| milestone: | none → 3.0 |
| status: | New → Invalid |
To post a comment you must log in.
Most of this code have been deleted. The security model is now view-based, since the interface is not longer built based on ZODB calls. Most of the screens have functional tests to ensure only the properly authenticated users, with the required level of authorization can access them (Selenium tests).