Closed (fixed)
Project:
Persistent Login
Version:
2.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
27 Jun 2023 at 07:13 UTC
Updated:
13 Jul 2023 at 01:29 UTC
Jump to comment: Most recent
Comments
Comment #2
auseidon986 commentedComment #3
auseidon986 commentedComment #4
chandreshgiri gauswami commentedI will work on it.
Comment #6
gappleThanks for opening the issue
Since the 2.x branch changed to using the authentication flow to check for a persistent login cookie only when needed, TokenHandler will only have its
$tokenproperty set on a user's first unauthenticated request (instead of every request, but not revalidating the token, like in 1.x). WhenclearSessionToken()is called on logout, it still assumed that the token property was already set from the request cookie, so skipped invalidating the token and the user was immediately re-initialized with a new session.The TokenHandler should now properly load the token if not done so already, in order to properly invalidate it when logging out.
Comment #7
gapple