@@ -137,7 +137,8 @@ Unauthenticated responses that are denied permission will result in an `HTTP 401
...
@@ -137,7 +137,8 @@ Unauthenticated responses that are denied permission will result in an `HTTP 401
**Note:** If you use `TokenAuthentication` in production you must ensure that your API is only available over `https` only.
**Note:** If you use `TokenAuthentication` in production you must ensure that your API is only available over `https` only.
=======
---
If you want every user to have an automatically generated Token, you can simply catch the User's `post_save` signal.
If you want every user to have an automatically generated Token, you can simply catch the User's `post_save` signal.
@receiver(post_save, sender=User)
@receiver(post_save, sender=User)
...
@@ -211,6 +212,15 @@ The following example will authenticate any incoming request as the user given b
...
@@ -211,6 +212,15 @@ The following example will authenticate any incoming request as the user given b
return (user, None)
return (user, None)
---
# Third party packages
The following third party packages are also available.
## Digest Authentication
HTTP digest authentication is a widely implemented scheme that was intended to replace HTTP basic authentication, and which provides a simple encrypted authentication mechanism. [Juan Riaza][juanriaza] maintains the [djangorestframework-digestauth][djangorestframework-digestauth] package which provides HTTP digest authentication support for REST framework.