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
I saw the recent announcement about the log_out_everywhere action—excited to see this functionality, thank you!
One key enhancement would be actively disconnecting all sockets associated with invalidated tokens. Currently, when a token is invalidated (e.g., via log_out_everywhere), live views or channels likely remain connected until something like a policy check or a fresh connection is attempted. Ideally, these sockets should be closed immediately when the token is invalidated.
This behavior should apply both when session tokens expire and when log_out_everywhere is triggered to ensure consistent session management.
Would love to hear your thoughts on this!
The text was updated successfully, but these errors were encountered:
I saw the recent announcement about the
log_out_everywhere
action—excited to see this functionality, thank you!One key enhancement would be actively disconnecting all sockets associated with invalidated tokens. Currently, when a token is invalidated (e.g., via
log_out_everywhere
), live views or channels likely remain connected until something like a policy check or a fresh connection is attempted. Ideally, these sockets should be closed immediately when the token is invalidated.This behavior should apply both when session tokens expire and when
log_out_everywhere
is triggered to ensure consistent session management.Would love to hear your thoughts on this!
The text was updated successfully, but these errors were encountered: