Bug #31677

Using current.securityContext Policies.yaml entities section triggers Parser Error

Added by Ferdinand Kuhl about 10 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Must have
Assignee:
-
Category:
Security
Start date:
2011-11-08
Due date:
% Done:

100%

Estimated time:
PHP Version:
Has patch:
No
Complexity:

Description

If you use some Content Security Rule like:

resources:
entities:
DigiComp_Fairdrive_Domain_Model_Disposition:
DigiComp_Fairdrive_ForeignDispositions: this.createdfrom != current.securityContext.party

FLOW3 will crash completely with:

: Parse error: syntax error, unexpected $end in [...]FLOW3/Data/Temporary/Development/Cache/Code/FLOW3_Object_Classes/TYPO3_FLOW3_Security_Aspect_PersistenceQueryRewritingAspect_Original.php(374) : eval()'d code


Related issues

Has duplicate TYPO3.Flow - Bug #32629: globalObjects are not available in the security (current.securityContext.party)ClosedKarsten Dambekalns2011-12-16

Actions

Also available in: Atom PDF