2 ms·
That doesn't seem difficult; just don't change the format of the session tokens. Eg a web application: you can substantially rewrite a web application, without
by kazinator 6y ago
That doesn't seem difficult; just don't change the format of the session tokens.
Eg a web application: you can substantially rewrite a web application, without invalidating logged in sessions.
The point here is that the logged in sessions were suspected of being unauthorized. The unauthorized sessions had to be turfed, and the clearest way of being sure that all unauthorized sessions are turfed is to delete all the sessions.
Of course, some those with unauthorized access will also try to log in to resume that unauthorized access, but presumably there is some trap laid for that.
Maybe for the accounts suspected of having been breached, there will be a mandatory password recovery procedure or whatever. Or they will monitor for suspicious logins from different IP addresses.
- pvg 6y agoYou can have state sitting in (serverside) session storage that is incompatible with the new version but you don't want users to lose. So now you have to migrate it, which can end up being actual work depending on the change.