如何访问请求对象在Sym2 FOSUserBundle自定义UserChecker

我使用Synfony2和FOSUserBundle，我有一个自定义userChecker，我想验证用户的主机(我们有几个主机指向相同的IP)。我的问题是，在我的自定义userChecker我不能访问请求，因此不是请求的主机。

这是我的用户检查代码

/*
 * This file is part of the Symfony package.
 *
 * (c) Fabien Potencier <fabien@symfony.com>
 *
 * For the full copyright and license information, please view the LICENSE
 * file that was distributed with this source code.
 */
//Override by Mattias
namespace BizTV'UserBundle'Controller;
//namespace Symfony'Component'Security'Core'User;
use Symfony'Component'Security'Core'Exception'CredentialsExpiredException;
use Symfony'Component'Security'Core'Exception'LockedException;
use Symfony'Component'Security'Core'Exception'DisabledException;
use Symfony'Component'Security'Core'Exception'AccountExpiredException;
use Symfony'Component'Security'Core'User'UserInterface;
use Symfony'Component'Security'Core'User'UserChecker as OriginalUserChecker;
use Symfony'Component'HttpFoundation'Request as Request; //ADDED BY MW
/**
 * UserChecker checks the user account flags.
 *
 * @author Fabien Potencier <fabien@symfony.com>
 */
class UserCheckerNew extends OriginalUserChecker
{
    /**
     * {@inheritdoc}
     */
    public function checkPreAuth(UserInterface $user)
    {
/*
        //Test for companylock...
        if ( !$user->getCompany()->getActive() ) {
            throw new LockedException('The company of this user is locked.', $user);
        }
        if ( $user->getLocked() ) {
            throw new LockedException('The admin of this company has locked this user.', $user);
        }
*/
        if (!$user instanceof AdvancedUserInterface) {
            return;
        }
        if (!$user->isCredentialsNonExpired()) {
            throw new CredentialsExpiredException('User credentials have expired.', $user);
        }

    }
    /**
     * {@inheritdoc}
     */
    public function checkPostAuth(UserInterface $user)
    {
        //Test for companylock...
        if ( !$user->getCompany()->getActive() ) {
            throw new LockedException('The company of this user is locked.');
        }    
        if ( $user->getLocked() ) {
            throw new LockedException('The admin of this company has locked this user.');
        }
/*
Validate HOST here
*/
        if (!$user instanceof AdvancedUserInterface) {
            return;
        }
        if (!$user->isAccountNonLocked()) {
            throw new LockedException('User account is locked.', $user);
        }
        if (!$user->isEnabled()) {
            throw new DisabledException('User account is disabled.', $user);
        }
        if (!$user->isAccountNonExpired()) {
            throw new AccountExpiredException('User account has expired.', $user);
        }
    }
}

在checkPostAuth函数中，我尝试了不同的东西，比如传递请求

public function checkPostAuth(UserInterface $user, Request $request)

错误提示我的重写必须符合原始/接口。

尝试在控制器中获取请求

$this->container->get('request_stack')->getCurrentRequest();

或者像这样

$currentHost = $request->getHost();

或者像这样

$cont = $this->getContainer();

或者像这样

$request = $this->getRequest();

或者像这样

$request = $container->get('request');

然而没有运气=)我不是Symfony2专家，正如你所看到的，我在这里只是随便说说=)

增加配置参数。根据gp- sflower的回答，我的配置。Yml现在看起来像这样:

services:
    security.user_checker:
        class: BizTV'UserBundle'Controller'UserCheckerNew
        arguments: [ "@request" ]
        scope: request
        public: true

在scope:request被添加到配置之前传递的错误是:

Scope Widening Injection detected: The definition "security.user_checker" references the service "request" which belongs to a narrower scope. Generally, it is safer to either move "security.user_checker" to scope "request" or alternatively rely on the provider pattern by injecting the container itself, and requesting the service "request" each time it is needed. In rare, special cases however that might not be necessary, then you can set the reference to strict=false to get rid of this error.'

当添加scope: request时，返回一个非常类似的错误

Scope Widening Injection detected: The definition "security.authentication.provider.dao.main" references the service "security.user_checker" which belongs to a narrower scope. Generally, it is safer to either move "security.authentication.provider.dao.main" to scope "request" or alternatively rely on the provider pattern by injecting the container itself, and requesting the service "security.user_checker" each time it is needed. In rare, special cases however that might not be necessary, then you can set the reference to strict=false to get rid of this error

添加public: true似乎没有什么不同。还有，我不知道这些公开的东西到底是什么意思，也许是安全问题?公众这个词总是让人害怕的=)