Introduce a new roles definition syntax including runtime constraints
|Status:||On Hold||Start date:||2010-02-25|
|Priority:||Could have||Due date:|
|Assignee:||Andreas Förthner||% Done:||
The roles definition in the Policy.yaml should look like that in the future:
constraint: party.name "andi" && party.address.street "at home"
Note the new feature of runtime constraints!
|related to TYPO3.Flow - Major Feature #5659: Implement content security||Resolved||2009-12-07|
Updated by Andreas Förthner about 3 years ago
- Status changed from Accepted to On Hold
- Priority changed from Should have to Could have
- Target version deleted (
1.0 alpha 8)
The role constraints should be implemented on the account side. As this feature seems not to be too important, we will postpone it until there's a real need for it.