dsj2014 2016-05-09 16:40
浏览 36
已采纳

带有FosUserBundle的Symfony 2.5:登录后将数据添加到全局会话

Our project uses the FOSUserBundle with Symfony 2.5. We need to add custom data to the user session after login, that resides in the database and is dynamic, but should be accessed in all templates and everywhere within the application.

I'm thinking about overriding the LoginManager.php class from /user-bundle/Security, but I'm also not entirely sure if that's the best possible option.

Looks like the logInUser() method is the place to add our custom change, given that it actually sets the token, but then again, if there's a smarter way to do that, I'll definitely go with it.

  • 写回答

1条回答 默认 最新

  • dourou9477 2016-05-10 06:24
    关注

    You can add a security interactive login listener, and in that listener you will have access to the login token that is stored in session. This token inherits Symfony\Component\Security\Core\Authentication\Token\AbstractToken so it has the methods "setAttribute($name, $value)" and "setAttributes(array $attributes)". Bassically whatever you set into this property with be stored in session alongside the user and the token.

    Just be careful about the fact that this is serialized and make sure if you store objects to implement the serialize/unserialize method if needed in order to not have circular reference problems.

    I recommended this approach because it seem to fit your requirements:

    • the token is already stored in session by symfony
    • the token is already accessible in any controller via the service "security.context" found in container,
    • the token is already accessible in twig using the code {{ app.security.getToken() }}

    For more information on Authentication Events check the symfony cookbook: http://symfony.com/doc/current/components/security/authentication.html#authentication-events

    Also you can use the following code as a guideline.

    In services yml

    security.interactive_login.listener:
            class: %security.interactive_login.listener.class%
            arguments: ['@security.context', '@session']
            tags:
                - { name: kernel.event_listener, event: security.interactive_login, method: onSecurityInteractiveLogin }
    

    In your listener

    use Symfony\Component\Security\Core\SecurityContextInterface;
    use Symfony\Component\HttpFoundation\Session\Session;
    use Symfony\Component\Security\Http\Event\InteractiveLoginEvent;
    
    class SecurityListener
    {
    
       public function __construct(SecurityContextInterface $security, Session $session)
       {
          $this->security = $security;
          $this->session = $session;
       }
    
       public function onSecurityInteractiveLogin(InteractiveLoginEvent $event)
       {
            $token = $event->getAuthenticationToken();
            $token->setAttribute('key','some stuff i want later');
       }
    
    }
    

    Hope this helps,

    Alexandru Cosoi

    本回答被题主选为最佳回答 , 对您是否有帮助呢?
    评论

报告相同问题?

悬赏问题

  • ¥15 FIR滤波器算法设计与实现(利用库函数firdec()
  • ¥15 利用单片机产生正弦信号,来测量差分放大电路放大倍数和共模放大倍数的思路和仿真
  • ¥60 关于mavlink的论文咨询
  • ¥66 定制开发肯德基自动化网站下单软件
  • ¥15 中科院研发的TextMind(文心)
  • ¥20 vscode虚拟环境依赖包未安装
  • ¥15 odoo17关于owl开发js代码问题
  • ¥15 光纤中多普勒频移公式的推导
  • ¥15 怎么制作一个人脸识别门禁系统
  • ¥20 大华dss监控平台网络关闭登不进去