On 14.01.2011, at 22:06, Jeremy Mikola wrote:
> I encountered a problem with this yesterday, attempting to override a
> firewall in our generic config for our test environment's config (which
> extends the generic). Since firewalls each get unique names upon processing,
> there's no way to override them... the first "main:" may become "main13414"
> and the second config's "main:" may be "main9890".
>
> Processing configs only once should indeed help this, provided they are
> permitted to overwrite each other. I suppose the merge-logic would be a
> subsequent "main:" block should completely override a previous "main:"?
I think the merge logic should "adding" anything new by default, however
setting something to false should disable it.
So for example:
# config.yml
security.config:
providers:
main:
id: fos_user.user_manager
firewalls:
main:
form_login:
login_path: /security/login
check_path: /security/login-check
anonymous: true
logout: true
# config_test.yml
security.config:
providers:
main:
id: fos_user.user_manager
firewalls:
main:
http-basic: true
form_login: false
Should result in the following in testing:
security.config:
providers:
main:
id: fos_user.user_manager
firewalls:
main:
http-basic: true
anonymous: true
logout: true
regards
Lukas Kahwe Smith
[email protected]
--
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 developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en
