Have you update your security configuration? All regexes must now be
"complete":
Before:
profiler:
pattern: /_profiler/.*
After:
profiler:
pattern: ^/_profiler
More information here:
https://github.com/symfony/symfony/blob/master/UPDATE.md
Fabien
--
Fabien Potencier
Sensio CEO - Symfony lead developer
sensiolabs.com | symfony.com | fabien.potencier.org
Tél: +33 1 40 99 80 80
On 4/4/11 11:10 PM, Christian Schaefer wrote:
hi all,
thanks for raising this topic. I experience the exact same behaviour.
I am still running on PR8 for that exact reason.
apparently the listener do not get called any longer.
I tried to hunt this down but run out of time and reverted back to
PR8.
I got as far as there is a method generated in app/cache/
appDevDebug..something that instantiates the security authentication
provider. It looked the same as in PR8 so there is nothing wrong with
the code generation.
but with PR8 it would die() when I enter one while in PR9 it would
never be called.
hope this puts someone in the right direction?
cheers
/Christian
On 4 Apr., 22:44, Dennis Jacobfeuerborn<djacobfeuerb...@gmail.com>
wrote:
On Monday, April 4, 2011 10:31:30 PM UTC+2, Christophe COEVOET wrote:
Le 04/04/2011 22:27, Dennis Jacobfeuerborn a écrit :
I just upgraded from PR8 to the current git state but this broke the
security stuff. Apparently the security component no longer handles the
_security_check route?
Unable to find the controller for path "/login_check". Maybe you forgot to
add the matching route in your routing configuration?
You need to define a controller as the listener intercept the request *
only* when the credentials are right. If they are wrong the request is not
intercepted and then goes to the controller (this was still the case
before).
I'm not sure I understand. How can the framework even determine if the
credentials are right if it doesn't intercept the /login_check call?
This code works fine in PR8 but apparently no longer in the current git
version and I didn't see any other required changes mentioned in the updates
file for the security component apart from the regexp changes for the
patterns.
Regards,
Dennis
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message because you are subscribed to the Google
Groups "symfony users" group.
To post to this group, send email to symfony-users@googlegroups.com
To unsubscribe from this group, send email to
symfony-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en
