Authentication backends documentation doesn't mention that backends are stored in Sessions.

[kyle.fox@…]

The ​Authentication Backends docs don't mention that when a User is successfully authenticated, the path to the backend that authenticated them is stored in a Session variable.

Problems can occur when you change settings.py from one custom backend to another backend. Django attempts to import the backend specified by the path in the session, so when a request comes from a User who has already authenticated through the previous backend an exception is raised.

A simple fix for this is Session.objects.all().delete(). However it should be noted that even after updating the AUTHENTICATION_BACKENDS setting, your application may still contain references to the old setting.

[(none)]

Milestone post-1.0 deleted

[Jacob]

(In [10371]) Fixed a whole bunch of small docs typos, errors, and ommissions.

Fixes #8358, #8396, #8724, #9043, #9128, #9247, #9267, #9267, #9375, #9409, #9414, #9416, #9446, #9454, #9464, #9503, #9518, #9533, #9657, #9658, #9683, #9733, #9771, #9835, #9836, #9837, #9897, #9906, #9912, #9945, #9986, #9992, #10055, #10084, #10091, #10145, #10245, #10257, #10309, #10358, #10359, #10424, #10426, #10508, #10531, #10551, #10635, #10637, #10656, #10658, #10690, #10699, #19528.

Thanks to all the respective authors of those tickets.

[Jacob]

Milestone 1.1 deleted