id,summary,reporter,owner,description,type,status,component,version,severity,resolution,keywords,cc,stage,has_patch,needs_docs,needs_tests,needs_better_patch,easy,ui_ux 12113,contrib.auth documentation is misleading re: whether User.is_active matters for login,Ethan Jucovy,nobody,"The documentation at source:/django//trunk/docs/topics/auth.txt says {{{ .. attribute:: models.User.is_active Boolean. Designates whether this user account should be considered active. Set this flag to ``False`` instead of deleting accounts. This doesn't control whether or not the user can log in. Nothing in the authentication path checks the ``is_active`` flag, so if you want to reject a login based on ``is_active`` being ``False``, it is up to you to check that in your own login view. However, permission checking using the methods like :meth:`~models.User.has_perm` does check this flag and will always return ``False`` for inactive users. }}} ""This doesn't control whether or not the user can log in."" This is technically true, but misleading, because the default `AuthenticationForm` in django.contrib.auth *does* reject inactive users. This behavior is undocumented.",,closed,Documentation,1.1,,fixed,,,Ready for checkin,1,0,0,0,0,0