You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a sub-issue of issue Ability to track and revoke sessions#20378
Brief:
The ultimate goal is to be able to look up all current sessions stored in active_record_store for a given user id. This will require finding a mechanism for storing the user id as part of the Rack session for indexed lookup.
Details:
The backing store for a session is based on the Settings.server.session_store value and is interpreted in the session_store initializer code.
There are three different types:
active_record_store ultimately ends up using the Session model
memory_store is in-memory
mem_cache_store ultimately uses Rack::Session::Dalli from the dalli gem.
In all cases, we use the underlying Rails session stores.
There will be a separate issue for each one of the three since each can be addressed separately, with separate PRs.
As the subject implies, this issue will be used to track the active_record_store case.
This is a sub-issue of issue Ability to track and revoke sessions #20378
Brief:
The ultimate goal is to be able to look up all current sessions stored in active_record_store for a given user id. This will require finding a mechanism for storing the user id as part of the Rack session for indexed lookup.
Details:
The backing store for a session is based on the
Settings.server.session_store
value and is interpreted in the session_store initializer code.There are three different types:
active_record_store
ultimately ends up using the Session modelmemory_store
is in-memorymem_cache_store
ultimately uses Rack::Session::Dalli from the dalli gem.In all cases, we use the underlying Rails session stores.
There will be a separate issue for each one of the three since each can be addressed separately, with separate PRs.
active_record_store
case.memory_store
work is tracked in Issue: #20464mem_cache_store
work is tracked in Issue: #20462The text was updated successfully, but these errors were encountered: