Task #2118
Decouple MVC and Security
| Status: | Resolved | Start date: | 2008-11-11 | |
|---|---|---|---|---|
| Priority: | Must have | Due date: | ||
| Assigned To: | Robert Lemke | % Done: | 100% |
|
| Category: | MVC | |||
| Target version: | TYPO3 Flow Base Distribution - 1.0 alpha 1 | |||
| Sprint: | Has patch: | |||
| PHP Version: | Complexity: |
Description
Remove dependencies between MVC and Security Framework (in Dispatcher)
Associated revisions
- FLOW3: (Security) Renamed the aspect InterceptorInvocation to PolicyEnforcementAspect
- FLOW3: (Security) Completely removed the security code from the MVC dispatcher. Instead it is now woven in by advices in the new RequestDispatchingAspect. Resolves #2118
- FLOW3: (Security) The old and the new aspect are now only active if security is enabled. That means: No security related proxies are generated if security is turned off. Addresses #2118
- FLOW3: (Security) Security is now (again) enabled by default. But that doesn't mean that everything is secure yet ...
- FLOW3: (AOP) Fixed the "Setting" poinctut designator by adding the class to the Objects configuration.
History
#1 Updated by Karsten Dambekalns over 6 years ago
- Category set to Security
By now security can be switched off, but there are still dependencies in the code.
#2 Updated by Robert Lemke over 6 years ago
- Category changed from Security to MVC
- Status changed from New to Accepted
- Assigned To set to Robert Lemke
#3 Updated by Robert Lemke over 6 years ago
- Status changed from Accepted to Resolved
- % Done changed from 0 to 100
Applied in changeset r1792.