CODEWITHSUNDEEP
phpsymfony
Adib Aroui
Adib Aroui

Reputation: 5067

Strange unexpected user logout - symfony 2.3.32

I really did all the best trying to resolve this issue with no avail. All similar questions on SO don't seem easy for me to understand. User get logged out after one page refresh, sometimes after two...there is no logic in this behaviour.

I am not familiar to log files, it is the first time I am reading them and I hope I am giving you the appropriate lines among the hundreds. By the way, these lines are about some internal Symfony stuff that I still don't get:

[2015-10-18 20:48:18] request.INFO: Matched route "user_admin_page" (parameters:"_controller": "Members\Bundle\ManagementBundle\Controller\AdminController::indexAction", "_route": "user_admin_page") [] []

.......

[2015-10-18 20:48:18] event.DEBUG: Notified event "kernel.request" to listener "Symfony\Component\Security\Http\Firewall::onKernelRequest". [] [] [2015-10-18 20:48:19] security.INFO: Populated SecurityContext with an anonymous Token [] []

[2015-10-18 20:48:19] event.DEBUG: Notified event "kernel.exception" to listener "Symfony\Component\Security\Http\Firewall\ExceptionListener::onKernelException". [] []

[2015-10-18 20:48:19] security.DEBUG: Access is denied (user is not fully authenticated) by "C:\xampp\htdocs\community\vendor\symfony\symfony\src\Symfony\Component\Security\Http\Firewall\AccessListener.php" at line 70; redirecting to authentication entry point [] []

[2015-10-18 20:48:19] security.DEBUG: Calling Authentication entry point [] []

[2015-10-18 20:48:19] event.DEBUG: Listener "Symfony\Component\Security\Http\Firewall\ExceptionListener::onKernelException" stopped propagation of the event "kernel.exception". [] []

......

[2015-10-18 20:48:19] event.DEBUG: Notified event "kernel.response" to listener "Symfony\Component\Security\Http\Firewall\ContextListener::onKernelResponse". [] []

[2015-10-18 20:48:19] security.DEBUG: Write SecurityContext in the session [] []

Your help is much appreciated.

Upvotes: 0

Views: 595

Answers (1)

Adib Aroui
Adib Aroui

Reputation: 5067

Thank you everybody for giving time to this issue. Apparently, here is the cause and possible solution:

In my website, I used Ratchet, which is a PHP library that provides real-time connections over websockets. To attach a web session to a websocket connection I used the Ratchet Session Provider:

The SessionProvider will attach a Symfony2 Session object to each incoming Connection object that will give you read-only access to the session data from your website. The SessionProvider will not work with any of the Native* session handlers. It is suggested you use choose one of the following Symfony Custom Save Handlers:

MemcacheSessionHandler MemcachedSessionHandler PdoSessionHandler (in development) RedisSessionHandler

I used the PdoSessionHandler, which brought a change in my configuration from:

framework:
    ...
    session:
      handler_id: ~

to: 

framework:
    ...
    session:
      handler_id: session.handler.pdo # old configuration that caused the

Switching back to old situation removes the issue. Possible solution then:

  • Use another approach in storing session data.
  • Upgrade from Symfony 2.3 to Symfony 2.6, according to docs, many enhancements were added to PdoSessionHandler wich requires additionnal changes in code.
  • Keep the same code, upgrade Symfony2 but change the handler name to LegacyPdoSessionHanlder.

Further details:

http://symfony.com/doc/current/cookbook/doctrine/pdo_session_storage.html http://socketo.me/docs/sessions

Other solutions that I don't see due to my limited knowlege are welcome.

Upvotes: 0

Related Questions