From 957700ecfb36322a8ea40ea473dc43ff1e92592f Mon Sep 17 00:00:00 2001
From: Tom Christie
Date: Tue, 13 Nov 2012 11:26:45 +0000
Subject: Remove OAuth2 from docs

---
 docs/api-guide/authentication.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

(limited to 'docs/api-guide/authentication.md')

diff --git a/docs/api-guide/authentication.md b/docs/api-guide/authentication.md
index c87ba83e..b2323d62 100644
--- a/docs/api-guide/authentication.md
+++ b/docs/api-guide/authentication.md
@@ -126,7 +126,7 @@ 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.
 
-## OAuth2Authentication
+<!--## OAuth2Authentication
 
 This authentication scheme uses the [OAuth 2.0][oauth] protocol to authenticate requests.  OAuth is appropriate for server-server setups, such as when you want to allow a third-party service to access your API on a user's behalf.
 
@@ -138,6 +138,7 @@ If successfully authenticated, `OAuth2Authentication` provides the following cre
 **TODO**: Note type of response (401 vs 403)
 
 **TODO**: Implement OAuth2Authentication, using django-oauth2-provider.
+-->
 
 ## SessionAuthentication
 
-- 
cgit v1.2.3