From f193270c89df766d6d5e55cb51ce2c205b63cc76 Mon Sep 17 00:00:00 2001 From: Derek McGowan Date: Mon, 26 Sep 2016 15:39:00 -0700 Subject: [PATCH] Add note about implementation of oauth2 Reading the oauth2 token documentation is misleading as it makes no mention of it being a newer feature which may not be supported by the token server. Add a note mentioning if it is not supported to refer to the token documentation for getting a token. Signed-off-by: Derek McGowan (github: dmcgowan) --- docs/spec/auth/oauth.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/spec/auth/oauth.md b/docs/spec/auth/oauth.md index 3d1ae0aa4..0f8d35dbb 100644 --- a/docs/spec/auth/oauth.md +++ b/docs/spec/auth/oauth.md @@ -15,6 +15,11 @@ This document describes support for the OAuth2 protocol within the authorization server. [RFC6749](https://tools.ietf.org/html/rfc6749) should be used as a reference for the protocol and HTTP endpoints described here. +**Note**: Not all token servers implement oauth2. If the request to the endpoint +returns `404` using the HTTP `POST` method, refer to +[Token Documentation](token.md) for using the HTTP `GET` method supported by all +token servers. + ## Refresh token format The format of the refresh token is completely opaque to the client and should be