-
Bug
-
Resolution: Fixed
-
Minor
-
4.4
-
MOODLE_404_STABLE
-
MOODLE_404_STABLE
-
MDL-81480-main -
-
2
-
Team Hedgehog 2024 Sprint 1.4
This issue was detected while executing MDLQA-18725. It seems the changes from MDL-63128 introduced a regression in the Redis session handler.
Steps to reproduce:
0) Have a localhost redis server configured and working.
1) Edit the config.php, remove any extra session configuration you have (just in case) and add the following lines:
$CFG->autologinguests = 0; |
$CFG->session_handler_class = '\core\session\redis'; |
$CFG->session_redis_host = '127.0.0.1'; |
$CFG->session_redis_port = 6379; // Optional. |
$CFG->session_redis_database = 0; // Optional, default is db 0. |
$CFG->session_redis_prefix = 'qa.sess.'; // Optional, default is don't set one. |
$CFG->session_redis_acquire_lock_timeout = 120; |
$CFG->session_redis_lock_expire = 7200; |
2) Purge caches executing: php admin/cli/purge_caches.php
3) Open a browser and login into the instance
4) In a terminal, execute: redis-cli flushall
5) Refresh the browser page
Expected: you should be redirected to the login page because the session is destroyed.
What happens: you are still logged in
- Discovered while testing
-
MDLQA-18725 CLONE - redis session handler can be used to manage users sessions
- Passed
- is a regression caused by
-
MDL-63128 Redis Cache & Session: implement cluster support
- Closed
- mentioned in
-
Page Loading...