From 4ca2820ff573ed87c70fedda69efa8de23955669 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Wed, 9 Jan 2019 18:22:29 -0500 Subject: [PATCH] Corrected whitespace in docs/ref/contrib/auth.txt. --- docs/ref/contrib/auth.txt | 37 ++++++++++++++++++------------------- 1 file changed, 18 insertions(+), 19 deletions(-) diff --git a/docs/ref/contrib/auth.txt b/docs/ref/contrib/auth.txt index 5e40aa7fc2..0dfa3a9261 100644 --- a/docs/ref/contrib/auth.txt +++ b/docs/ref/contrib/auth.txt @@ -69,7 +69,7 @@ Fields .. attribute:: user_permissions - Many-to-many relationship to :class:`~django.contrib.auth.models.Permission` + Many-to-many relationship to :class:`~django.contrib.auth.models.Permission` .. attribute:: is_staff @@ -482,7 +482,6 @@ backends, see the :ref:`Other authentication sources section ` of the :doc:`User authentication guide `. - Available authentication backends --------------------------------- @@ -566,14 +565,14 @@ The following backends are available in :mod:`django.contrib.auth.backends`: .. class:: AllowAllUsersModelBackend - Same as :class:`ModelBackend` except that it doesn't reject inactive users - because :meth:`~ModelBackend.user_can_authenticate` always returns ``True``. + Same as :class:`ModelBackend` except that it doesn't reject inactive users + because :meth:`~ModelBackend.user_can_authenticate` always returns ``True``. - When using this backend, you'll likely want to customize the - :class:`~django.contrib.auth.forms.AuthenticationForm` used by the - :class:`~django.contrib.auth.views.LoginView` by overriding the - :meth:`~django.contrib.auth.forms.AuthenticationForm.confirm_login_allowed` - method as it rejects inactive users. + When using this backend, you'll likely want to customize the + :class:`~django.contrib.auth.forms.AuthenticationForm` used by the + :class:`~django.contrib.auth.views.LoginView` by overriding the + :meth:`~django.contrib.auth.forms.AuthenticationForm.confirm_login_allowed` + method as it rejects inactive users. .. class:: RemoteUserBackend @@ -608,16 +607,16 @@ The following backends are available in :mod:`django.contrib.auth.backends`: .. method:: clean_username(username) - Performs any cleaning on the ``username`` (e.g. stripping LDAP DN - information) prior to using it to get or create a user object. Returns - the cleaned username. + Performs any cleaning on the ``username`` (e.g. stripping LDAP DN + information) prior to using it to get or create a user object. Returns + the cleaned username. .. method:: configure_user(user) - Configures a newly created user. This method is called immediately - after a new user is created, and can be used to perform custom setup - actions, such as setting the user's groups based on attributes in an - LDAP directory. Returns the user object. + Configures a newly created user. This method is called immediately + after a new user is created, and can be used to perform custom setup + actions, such as setting the user's groups based on attributes in an + LDAP directory. Returns the user object. .. method:: user_can_authenticate() @@ -629,9 +628,9 @@ The following backends are available in :mod:`django.contrib.auth.backends`: .. class:: AllowAllUsersRemoteUserBackend - Same as :class:`RemoteUserBackend` except that it doesn't reject inactive - users because :attr:`~RemoteUserBackend.user_can_authenticate` always - returns ``True``. + Same as :class:`RemoteUserBackend` except that it doesn't reject inactive + users because :attr:`~RemoteUserBackend.user_can_authenticate` always + returns ``True``. Utility functions =================