Major Feature #5659

Implement content security

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

Status:
Resolved
Priority:
Must have
Category:
Security
Target version:
-
Start date:
2009-12-07
Due date:
% Done:

0%

Estimated time:
PHP Version:
Has patch:
Complexity:

Description

This ticket is a placeholder for all commits related to content security. Obviously this feature still needs to be described properly.

In general, content security will be handled by aspects affecting the persistence framework enforcing policies for all kinds of operations related to content (i.e. objects and their properties).


Related issues

Related to TYPO3.Flow - Feature #4960: There should be a Request hash check when objects are modifiedResolvedSebastian Kurfuerst2009-10-09

Actions
Related to TYPO3.Flow - Feature #3618: Extended ACL possibilitiesClosedAndreas Förthner2009-06-08

Actions
Related to TYPO3.Flow - Task #6599: Implement new syntax for policy resources including runtime constraintsResolvedAndreas Förthner2010-02-25

Actions
Related to TYPO3.Flow - Task #6600: Remove the privilege concept vom ACLsResolvedAndreas Förthner2010-02-25

Actions
Related to TYPO3.Flow - Task #6601: Introduce a new roles definition syntax including runtime constraintsOn HoldAndreas Förthner2010-02-25

Actions
Related to TYPO3.Flow - Feature #6604: Implement QueryRewriting according to the security policyResolvedAndreas Förthner2010-03-04

Actions
Related to TYPO3.Flow - Feature #6605: Integrate the security policy into resource managementResolvedAndreas Förthner

Actions
Related to TYPO3.Flow - Feature #8463: Check security policy for objects reconstituted in the session scopeNew2010-06-23

Actions
Related to TYPO3.Flow - Feature #9968: Promote security publishing configuration automatically when persisting modelsNewAndreas Förthner2010-09-28

Actions

Also available in: Atom PDF