Custom Expression Language function not working in @Security annotation #21305

mrsuh · 2017-01-16T14:40:13Z

Q	A
Bug report?	yes
Feature request?	no
BC Break report?	no
RFC?	no
Symfony version	3.1.9

AppBundle\ExpressionLanguage\ExpressionLanguageProvider;

<?php

namespace AppBundle\ExpressionLanguage;

use Symfony\Component\ExpressionLanguage\ExpressionFunction;
use Symfony\Component\ExpressionLanguage\ExpressionFunctionProviderInterface;

class ExpressionLanguageProvider implements ExpressionFunctionProviderInterface
{
    public function getFunctions()
    {
        return array(
            new ExpressionFunction('test', function ($input) {
                return $input;
            }, function (array $values, $input) {
                return $input;
            }),
        );
    }
}

services.yml

    app.security_expression_language_provider:
        class: AppBundle\ExpressionLanguage\ExpressionLanguageProvider
        tags:
            - { name: security.expression_language_provider }

AppBundle\Controller\MyController;

<?php

namespace AppBundle\Controller;

use Sensio\Bundle\FrameworkExtraBundle\Configuration\Security;
use Symfony\Component\HttpFoundation\Response;

class MyController extends Controller
{
    /**
    * @Security("test()")
    */
    public function listAction(Request $request)
    {
       return new Response();
    }
}

Error: The function "test" does not exist around position 1.

dmaicher · 2017-01-28T12:51:23Z

The problem is actually within the SensioFrameWorkExtraBundle which does not register custom expression language providers.

I proposed a fix here: https://github.com/sensiolabs/SensioFrameworkExtraBundle/pull/452/files#diff-c27855d16cebd806adb50a74554fa567R18

For now you could just add the compiler pass within your App to register your new functions.

jakzal · 2017-02-08T18:16:19Z

Closing here, as the actual work needs to be done in the SensioFrameworkExtraBundle.

…cher) This PR was merged into the 3.0 branch. Discussion ---------- Register tagged security expression language providers Custom security expression language providers are currently not registered which leads to issue symfony/symfony#21305. Commits ------- f8c19d7 Register tagged security expression language providers

javiereguiluz changed the title ~~[Bug] Extra Language Expression not working in Security Annotation~~ Custom Expression Language function not working in @Security annotation Jan 16, 2017

javiereguiluz added Bug ExpressionLanguage Unconfirmed labels Jan 16, 2017

carsonbot added the Status: Needs Review label Jan 16, 2017

dmaicher mentioned this issue Jan 28, 2017

Register tagged security expression language providers sensiolabs/SensioFrameworkExtraBundle#452

Merged

jakzal closed this as completed Feb 8, 2017

syrm mentioned this issue Jun 16, 2017

Custom Expression Language function not working in security.yml allow_if #23208

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Custom Expression Language function not working in @Security annotation #21305

Custom Expression Language function not working in @Security annotation #21305

Custom Expression Language function not working in @Security annotation #21305

Custom Expression Language function not working in @Security annotation #21305

Comments