Closed Osmose closed 10 years ago
Alternatively, according to @Sancus , changing the cookie name works too.
9 months ago I thought upgrading meant changing the authentication backend name, now I cannot find any hint of that being the case. Unless someone can find where this happened, let's just reduce this issue to including upgrade docs.
We should really have some docs explaining how to upgrade to the latest django-browserid since the last version bump was a huge change.
More importantly, we should mention this django bug: https://code.djangoproject.com/ticket/18998
Upgrading includes changing the name of the authentication backend, which causes nasty tracebacks for users with existing sessions. A recommendation to clear all sessions might be useful to note.