... ails could be leaked. This issue is fixed with the caveat that AuthenticationForm can no longer raise the "This account is inactive." error if the authentication backend rejects inactive users (the default authentication backend, ModelBackend , has done ... allowed AuthenticationForm authentication backend Fixed model バグ 修正 regression incorrect user overridden issue caveat inactive foreign リリースノート 1日 セキュリティ 問題 情報漏えい made method クイック検索 Last update: 2026年10月09日 « previous | ... ... ails could be leaked. This issue is fixed with the caveat that AuthenticationForm can no longer raise the "This account is inactive." error if the authentication backend rejects inactive users (the default authentication backend, ModelBackend , has done ... allowed AuthenticationForm authentication backend Fixed model バグ 修正 regression incorrect user overridden issue caveat inactive foreign リリースノート 関連するページ Django 2.0.2 リリースノート Django 1.11.9 リリースノート Django 1.5.12 リリースノート ... ... ails could be leaked. This issue is fixed with the caveat that AuthenticationForm can no longer raise the "This account is inactive." error if the authentication backend rejects inactive users (the default authentication backend, ModelBackend , has done ... irm login allowed AuthenticationForm authentication backend model crashes バグ 修正 incorrect user overridden issue caveat inactive foreign doesn リリースノート 1日 セキュリティ 問題 情報漏えい クイック検索 Last update: 2026年10月09日 « previous | up | n ... ... ails could be leaked. This issue is fixed with the caveat that AuthenticationForm can no longer raise the "This account is inactive." error if the authentication backend rejects inactive users (the default authentication backend, ModelBackend , has done ... irm login allowed AuthenticationForm authentication backend model crashes バグ 修正 incorrect user overridden issue caveat inactive foreign 関連するページ Django 1.11.10 リリースノート Django 1.11.9 リリースノート Django 1.5.12 リリースノート Django 1.9. ... ... been added to the memcached cache backend. For more details, see the documentation on caching in Django . Permissions for inactive users ¶ If you provide a custom auth backend with supports_inactive_user set to True , an inactive User instance will chec ... use the read operation that retrieves the MyObject instance leaves the transaction in a dirty state. No password reset for inactive users ¶ Prior to Django 1.3, inactive users were able to request a password reset email and reset their password. In Djang ... o 1.3 inactive users will receive the same message as a nonexistent account. Password reset view now accepts from_email ¶ The django.cont ... ... been added to the memcached cache backend. For more details, see the documentation on caching in Django . Permissions for inactive users ¶ If you provide a custom auth backend with supports_inactive_user set to True , an inactive User instance will chec ... use the read operation that retrieves the MyObject instance leaves the transaction in a dirty state. No password reset for inactive users ¶ Prior to Django 1.3, inactive users were able to request a password reset email and reset their password. In Djang ... o 1.3 inactive users will receive the same message as a nonexistent account. Password reset view now accepts from_email ¶ The django.cont ... ... .10, AuthenticationForm to raise the inactive user error when using ModelBackend ( #28645 ). Added support for QuerySet.values() and values_list() for union() , differe ... e crash MySQL uses nulls リリースノート December fixes several bugs バグ 修正 Reallowed following AuthenticationForm raise inactive user クイック検索 Last update: 2026年10月09日 « previous | up | next » ... ... .10, AuthenticationForm to raise the inactive user error when using ModelBackend ( #28645 ). Added support for QuerySet.values() and values_list() for union() , differe ... ... e tag library. The reset and sqlreset management commands will be removed. Authentication backends will need to support an inactive user being passed to all methods dealing with permissions. The supports_inactive_user attribute will no longer be checked ... and has been replaced by the nb language code. Authentication backends will need to define the boolean attribute supports_inactive_user until version 1.5 when it will be assumed that all backends will handle inactive users. django.db.models.fields.XMLFi ... ... および AllowAllUsersRemoteUserBackend は、 User.is_active の値を無視します。一方、 ModelBackend および RemoteUserBackend は inactive なユーザーを拒否するようになりました。 django.contrib.gis ¶ Distance lookups は、distance value パラメータとして、式 (expr ... xecute() , pass the command object as the first argument to call_command() . ModelBackend and RemoteUserBackend now reject inactive users. This means that inactive users can't login and will be logged out if they are switched from is_active=True to False ... UTHENTICATION_BACKENDS instead. In light of the previous change, the test client's login() method no longer always rejects inactive users but instead delegates this decision to the authentication backend. force_login() also delegates the decision to the ... 2026年10月08日