Workaround Needed for Cookie Validation Issue During Django Upgrade

[webjunkie]

We've encountered an issue related to two-factor authentication cookie validation after a major Django version upgrade, as detailed in issue #686. This issue arises due to the change in user password hashes when Django's hash iteration count is updated in a new version, leading to a mismatch in the two-factor authentication cookies' validation.

We can for now implement a workaround. This involves catching the BadSignature exception raised during the cookie validation process when there's a mismatch in the hashes. This situation occurs after upgrading Django, which causes the user's password hash to change, thereby invalidating the existing two-factor authentication cookies.

This issue is critical for us to upgrade our Django version without disrupting the user experience of people coming back and having a 2FA cookie.