Skip to content

[SecurityBundle] Merged configuration between ENVs generates a strange behavior #40404

Closed
@liarco

Description

@liarco

Symfony version(s) affected: 5.2.4 (maybe also 4.4.x? see StackOverflow reference below)

Description
Setting access_decision_manager.strategy from the main /config/packages/security.yaml file while using other /config/packages/ENV/security.yaml files to fine-tune some other options results in the strategy value being overridden by the default (affirmative).

I think that this may be related to: https://stackoverflow.com/questions/61520675/symfony-access-decision-manager-strategy-is-always-affirmative

Am I doing anything wrong?

How to reproduce
Here is a reproducer: https://github.com/liarco/symfony-access-decision-strategy-config (the README contains complete instructions and output examples).


Thank you for your time.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions