Task #2118

Decouple MVC and Security

Added by Robert Lemke almost 11 years ago. Updated almost 9 years ago.

Status:
Resolved
Priority:
Must have
Assignee:
Category:
MVC
Start date:
2008-11-11
Due date:
% Done:

100%

Sprint:
PHP Version:
Has patch:
Complexity:

Description

Remove dependencies between MVC and Security Framework (in Dispatcher)

Associated revisions

Revision aa95e6e5 (diff)
Added by Robert Lemke over 10 years ago

  • 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 10 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 10 years ago

  • Category changed from Security to MVC
  • Status changed from New to Accepted
  • Assignee set to Robert Lemke

#3 Updated by Robert Lemke over 10 years ago

  • Status changed from Accepted to Resolved
  • % Done changed from 0 to 100

Applied in changeset r1792.

Also available in: Atom PDF