This indirectly fixes two bugs in Silex regarding Security and Twig.

The first is if twig is loaded before boot() some services/parameters are not defined.

• twig asks for security.authorization_checker
• security.authorization_checker asks for security.authentication_manager
• security.authentication_manager asks for security.authentication_providers
• security.authentication_providers are not completely defined until security.firewall_map is loaded (here).

I fixed this locally by wrapping the security.authorization_checker service and loading the security.firewall_map before hand:

// Load firewall map before this, because it defines a dependency needed.
$factory = $app->raw('security.authorization_checker');
$app['security.authorization_checker'] = function ($app) use ($factory) {
    $app['security.firewall_map'];

    return $factory($app);
};

This technically fixed the problem, but it wouldn't be needed if the service wasn't loaded until boot() where the firewall is loaded by default.

The second problem is a circular dependency. I was implementing an AccessDeniedHandler that rendered a template.

• security.firewall_map asks for AccessDeniedHandler service
• AccessDeniedHandler service asks for twig
• twig asks for security.firewall_map ....:boom:

And again this wouldn't be a problem if twig didn't need the SecurityRuntime until it's is_granted is called.

I don't see this as a feature since it only modifies private services. And I do see this as a bugfix even though it's for Silex and not Symfony. But I know it's a gray area. Twig Runtimes seem to be the way we are heading so I don't think this is a step in the wrong direction either.

I have a PR ready for Silex depending on the direction of this issue. Here's the diff.