From 0400cbbc4cd20dc7f70a077600e240c504900341 Mon Sep 17 00:00:00 2001 From: aaronykng Date: Mon, 27 Mar 2017 12:08:07 -0700 Subject: [PATCH] Added drfpasswordless to Authentication docs --- docs/api-guide/authentication.md | 19 +------------------ 1 file changed, 1 insertion(+), 18 deletions(-) diff --git a/docs/api-guide/authentication.md b/docs/api-guide/authentication.md index 8e6c9d89b..2344c68e3 100644 --- a/docs/api-guide/authentication.md +++ b/docs/api-guide/authentication.md @@ -358,24 +358,7 @@ HTTP Signature (currently a [IETF draft][http-signature-ietf-draft]) provides a ## drfpasswordless -[drfpasswordless][drfpasswordless] adds passwordless support to Django Rest Framework's own TokenAuthentication scheme. Users log in and sign up with a token sent to a contact point, either an email address or a mobile number. - -#### Example - - curl -X POST -d "email=aaron@example.com" localhost:8000/auth/email/ - -User receives an email: - - .. -

Your login token is 123456

- .. - -The client has 15 minutes to provide the correct token in exchange for an authentication token (provided by Django Rest Framework's Token Authentication). - - curl -X POST -d "token=815381" localhost:8000/callback/auth/ - - > HTTP/1.0 200 OK - > {"token":"76be2d9ecfaf5fa4226d722bzdd8a4fff207ed0e”} +[drfpasswordless][drfpasswordless] adds (Medium, Square Cash inspired) passwordless support to Django REST Framework's own TokenAuthentication scheme. Users log in and sign up with a token sent to a contact point like an email address or a mobile number. [cite]: http://jacobian.org/writing/rest-worst-practices/ [http401]: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.2