diff options
| author | rowanv <rrvspam@gmail.com> | 2016-01-24 22:26:11 +0100 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2016-02-01 10:42:05 -0500 |
| commit | a6ef025dfb2a1d1bd23893408eef6d066fb506d9 (patch) | |
| tree | b29b3624a20cc65184c743102e0f5f620412105f /docs/topics/auth/default.txt | |
| parent | 8bf8d0e0ecc1805480deb94feb4675b09d3b3a95 (diff) | |
Fixed #26124 -- Added missing code formatting to docs headers.
Diffstat (limited to 'docs/topics/auth/default.txt')
| -rw-r--r-- | docs/topics/auth/default.txt | 19 |
1 files changed, 10 insertions, 9 deletions
diff --git a/docs/topics/auth/default.txt b/docs/topics/auth/default.txt index e59f0318cc..5b6472f7a3 100644 --- a/docs/topics/auth/default.txt +++ b/docs/topics/auth/default.txt @@ -17,8 +17,8 @@ are somewhat coupled. .. _user-objects: -User objects -============ +``User`` objects +================ :class:`~django.contrib.auth.models.User` objects are the core of the authentication system. They typically represent the people interacting with @@ -112,7 +112,7 @@ passwords. Changing a user's password will log out all their sessions. See :ref:`session-invalidation-on-password-change` for details. -Authenticating Users +Authenticating users -------------------- .. function:: authenticate(\**credentials) @@ -363,13 +363,14 @@ If you have an authenticated user you want to attach to the current session :func:`~django.contrib.auth.login()`. Now you can set the backend using the new ``backend`` argument. -Selecting the :ref:`authentication backend <authentication-backends>` -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +Selecting the authentication backend +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ When a user logs in, the user's ID and the backend that was used for authentication are saved in the user's session. This allows the same -authentication backend to fetch the user's details on a future request. The -authentication backend to save in the session is selected as follows: +:ref:`authentication backend <authentication-backends>` to fetch the user's +details on a future request. The authentication backend to save in the session +is selected as follows: #. Use the value of the optional ``backend`` argument, if provided. #. Use the value of the ``user.backend`` attribute, if present. This allows @@ -1673,7 +1674,7 @@ model. Groups can be created, and permissions can be assigned to users or groups. A log of user edits to models made within the admin is also stored and displayed. -Creating Users +Creating users -------------- You should see a link to "Users" in the "Auth" @@ -1695,7 +1696,7 @@ non-superuser the ability to edit users, this is ultimately the same as giving them superuser status because they will be able to elevate permissions of users including themselves! -Changing Passwords +Changing passwords ------------------ User passwords are not displayed in the admin (nor stored in the database), but |