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'm actually not sure whether this is a bug or if I'm just misunderstanding something. The docs for Alternative Tokens say:
This way you are free to change the user’s alternative id to a new randomly generated value when the user changes their password, which would ensure their old authentication sessions will cease to be valid.
Once I change the alternative id, I get a RecursionError if I try to do anything with current_user. The only way I've found to avoid it is to immediately log the current user out, but is that what I'm supposed to do? Is there some easy way I'm missing to keep the current session valid after changing the alternative id?
The text was updated successfully, but these errors were encountered:
I'm actually not sure whether this is a bug or if I'm just misunderstanding something. The docs for Alternative Tokens say:
Once I change the alternative id, I get a RecursionError if I try to do anything with
current_user
. The only way I've found to avoid it is to immediately log the current user out, but is that what I'm supposed to do? Is there some easy way I'm missing to keep the current session valid after changing the alternative id?The text was updated successfully, but these errors were encountered: