Just wondering if we shouldn't investigate about @ro0NL 's comment about creating something like a FirewallConfigManager/Registry instead:

FirewallConfigRegistry::get(string $name) : FirewallConfig
FirewallConfigRegistry::fromRequest(Request $request) : FirewallConfig
FirewallConfigRegistry::current() : FirewallConfig
FirewallConfigRegistry::all() : FirewallConfig[]
FirewallConfigRegistry::inContext(string $context) : FirewallConfig[]

Maybe we could even remove the config from the FirewallContext and FirewallMap in favor of using the FirewallConfigRegistry as main entrypoint.

This would definitely be a better approach. Is someone working on it already?

Nobody AFAIK. I'd like to give a look tomorrow if I've got some time.
But if you're pleased by this idea in order to rework your PR (or a new one) differently, feel free to do so!

@julienfalque : See #20591 && #20592

After all, listing available firewalls is not a common need, as well as accessing the firewall configuration (usage being mostly internal at the moment). If some other use cases appear, we could think to reopen this PRs but for now, isn't it doable to decorate the FirewallMap service from user code?