Error : security.yml firewall parameter error

[Ph3nol]

Hi,

An error seems to exist with "wsse" security.yml firewall parameter.

Here is returned error: InvalidConfigurationException: Unrecognized options "wsse" under "security.firewalls.wsse_secured".

An idea to fix it?

Thank you.

[djoos]

Hi P3nol,

it sounds like there's something missing/incorrect from the steps outlined in README.md... Could you double-check app/autoload.php and app/AppKernel.php?

If that still doesn't help to clear up the issue, don't hesitate to contact me!

Kind regards, David

[Ph3nol]

I've double-checked my app/autoload.php and app/AppKernel.php files, no problem with loading the bundle.

Every step of README file is OK. I'll take a look to your bundle to understand what could be the problem (if there is one of course!).

Thank you for your help!

[djoos]

You're welcome! Would you mind sending over your security.yml so I can have a look at it? If the plugin loads correctly, I have the feeling the key might be over there... Do remove any sensitive information, obviously :-)

You can either copy/paste it here or send it to me via david@escapestudios.com...

[Ph3nol]

Here is my security.yml: https://gist.github.com/be9029ea946897351b6f

[djoos]

Hi,

thanks for sending me over the gist. It doesn't look there's anything wrong at all in that file...

Now, it is an InvalidConfigurationException, so "somewhere" in the config there must be "something" wrong... :-D

I've tried replicating the issue, using your security.yml, in a couple of our applications where we use the bundle and it works without giving any issues. When deliberately changing the wsse_secured "wsse" option to "wssea" I do run into the same issue, but when using the proper wsse-option there's no problem at all. Not sure what is going on exactly - it's normally pretty straightforward to implement the bundle...

Which version of SF2 have you got installed? (I tried on both 2.0.9 and 2.0.10) Any particular bundles?

Kind regards, David

[djoos]

Hi Ph3nol,

how are you doing with the issue?

Thanks in advance for your feedback!

King regards, David

[rjarteta]

Hi @djoos I'm having the exact same problem, no idea what can be wrong. Maybe a bad codification in the security.yml file (Working in both linux and Windows). Windows + Eclipse (Aptana) won't work. Have you stumble with this issue in yml files ?

[djoos]

Hi Ricardo,

could you let me know which version of SF2 you've got installed? If possible, could you send me your security.yml?

Thanks in advance!

Kind regards, David

[rjarteta]

Hi @djoos.

According to deps file: version=origin/2.0

https://gist.github.com/3420191

[djoos]

Hi Ricardo,

hmm, can't see anything immediately stands out... Would you mind posting the stack trace? That might give me a better idea of where to look!

Thanks!

Kind regards, David

[rjarteta]

Hi David, This helps? https://gist.github.com/3426631

Let me know if there's anything I can do to help you.

Thanks a lot for your help!

[djoos]

Hi rjarteta,

similar to when P3nol reported this issue, I'm not being able to spot anything obvious that is wrong nor can we replicate the issue... Could you send me the deps.lock line for symfony? Just to get some idea of which exact version of the 2.0 version you're using.

It would be great if you could try to give it a go in a fresh and clean Symfony2 project, install the WSSE authentication bundle there and see whether that replicates the issue. If so, do share the project with us and then we can check it out and dig deeper... We do understand this is probably not possible on the project you're working on right now.

Hope this helps!

Kind regards, David

[rjarteta]

No problem!! I can create a new project with only WSSE authentication bundle and see if that works.

I run the php bin/vendors update a couple of hours ago (The problem keeps showing up).

The deps.lock:

symfony 07d108af5ec88b20efd1faf8931e15ec5b89df15 twig v1.8.2 monolog 1.0.2 doctrine-common 2.1.4 doctrine-dbal 2.1.7 doctrine 2.1.7 swiftmailer v4.2.0 assetic v1.0.3 twig-extensions feb6d3f10c411e2631997c0a905aa581c80305c1 metadata 1.0.0 SensioFrameworkExtraBundle 85911039aca2ef39805640d9238c7157d8c30d2e JMSSecurityExtraBundle e752f888c51425f71382c056961f10f2be642102 SensioDistributionBundle 41a6c5caed65f02bb09c95a90579f047616471fd SensioGeneratorBundle c0118ce370f8da20e43051f2dd1ae331a202ab9c AsseticBundle 6f15728c1aefa5246caa83730e3dbf70b0d46052 Zend\Soap ac506518409789376ed9a73c56e7337cd1efcdef Zend\Mime c3aa7365c20aa3b62cabff4f65d6c943fff0e03c BeSimple\SoapCommon 51e6f0f689b18e1301570f18995b6fd5f8282fa9 BeSimple\SoapServer 8dace85c50986e3c5c8cbb96436ad2d0d904257d BeSimpleSoapBundle 4741e142d0222e7f037278420db4bd40bf9872a6 BeSimple\SoapClient 6a4fba600fa9b51861866c6e7d16f1e737c98096 EscapeWSSEAuthenticationBundle 9f65d8247a434ace4ef1ee98c7f8fae09c8e5532

[djoos]

Perfect, let me know how it goes - thanks in advance!

[rjarteta]

Oh no!!! I just fix it!! Sorry for bother you!

The factories parameter was missing, copy + paste from the installation instructions and Symfony is running again.

Thanks a lot for your time!

[djoos]

Hi Ricardo,

oh, sorry: I should have spotted that in the gist you posted earlier...

I'm glad the issue has been resolved now! I'm quite sure this might be a recurring issue, so great to have the solution documented here.

Have a great day!

Kind regards, David

[djoos]

On another note: please pull down a new version of the bundle: take out the EscapeWSSEAuthenticationBundle line in your deps.lock or update it manually to the new commit. I just made a change as in the configuration a non-existing class was used...

Don't hesitate to open up another issue if you have any other questions about the bundle!

Kind regards, David

[rjarteta]

Updated!

From https://github.com/escapestudios/EscapeWSSEAuthenticationBundle 9f65d82..34abd38 master -> origin/master HEAD is now at 34abd38 There's no WSSEFactory - use Factory instead

Thanks a lot for your help!

[djoos]

You're welcome - have a great day/evening!