Bug #12917

Access denied by using the HashService Setter injection

Added by Julian Kleinhans almost 11 years ago. Updated about 10 years ago.

Must have
Start date:
Due date:
% Done:


Estimated time:
PHP Version:
Has patch:


[See https://review.typo3.org/#change,699]

If i use the HashService Setter injection in a protected area as a loggedin user i became an "Access denied"

this is my Policy.yaml

    F3_Tutorials_RestrictedAdminArea: 'class(F3\Tutorials\Controller\Admin\.*)'
  Administrator: []
      F3_Tutorials_RestrictedAdminArea: GRANT

in the Controller\Admin i used a setter injection for the HashService.

public function injectHashService(\F3\FLOW3\Security\Cryptography\HashService $hashService) {
  $this->hashService = $hashService;

and with this method in my code i become the "Access denied" page.. my logs:

Successfully re-authenticated tokens for account "test1" [logged in F3\FLOW3\Security\Aspect\LoggingAspect::logManagerAuthenticate()]

Access denied (0 denied, 0 granted, 1 abstained) to method F3\Tutorials\Controller\Admin\AccountController::injectHashService(). [logged in F3\FLOW3\Security\Aspect\LoggingAspect::logJoinPointAccessDecisions()]

if i used the property injection

* @inject
* @var \F3\FLOW3\Security\Cryptography\HashService
protected $hashService;

it works without problems.. only with the setter injection There is NO other ACL in a policy.yaml


Updated by Christopher Hlubek over 10 years ago

I had a similar problem that I solved with a different pointcut. I changed the Controller->.*() to Controller->(?!inject)[a-z].*() such that the Policy will not be applied to inject methods.

I consider this as a workaround. The Policy shouldn't be applied to inject methods at all, since the authentication might not be initialized when injecting dependencies.


Updated by Sebastian Kurfuerst over 10 years ago

  • Target version changed from 1.0 beta 1 to 1.0 beta 2

we won't manage this for beta1 anymore, postproning


Updated by Robert Lemke about 10 years ago

  • Status changed from New to Accepted
  • Assignee set to Robert Lemke

Updated by Robert Lemke about 10 years ago

  • Status changed from Accepted to Rejected

I have thought about this one. As I see it, FLOW3 behaves correctly and we shouldn't change the behavior.

The point is, if we'd exclude all inject*() methods from the policies by default, we wouldn't solve the whole problem, because there can still be regular setters (setFoo()) which are used for Dependency Injection. Granting access to any setter by default and even if you explicitly create a policy which doesn't allow access to Class->.* would be dangerous.

Therefore, if the Access Denied exception tells that a method injectSomething() couldn't be called, that should be enough information for either switching to property injection, like Julian did, or adjusting the policy, like Christopher did.


Updated by Julian Kleinhans about 10 years ago

Ok, so we should add this information to the wiki error page

Also available in: Atom PDF