manifoldcf-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1488945 - /manifoldcf/trunk/site/src/documentation/content/xdocs/en_US/end-user-documentation.xml
Date Mon, 03 Jun 2013 09:52:45 GMT
Author: kwright
Date: Mon Jun  3 09:52:45 2013
New Revision: 1488945

Clarify the OAuth process


Modified: manifoldcf/trunk/site/src/documentation/content/xdocs/en_US/end-user-documentation.xml
--- manifoldcf/trunk/site/src/documentation/content/xdocs/en_US/end-user-documentation.xml
+++ manifoldcf/trunk/site/src/documentation/content/xdocs/en_US/end-user-documentation.xml
Mon Jun  3 09:52:45 2013
@@ -1729,7 +1729,7 @@ curl -XGET http://localhost:9200/index/_
               <figure src="images/en_US/googledrive-repository-setup-2.PNG" alt="googledrive
enable drive api" width="80%"/>
-              <p>Then going to the API Access link on the righthand side, we need to
select create an OAutg 2.0 client ID:</p>
+              <p>Then going to the API Access link on the righthand side, we need to
select create an OAuth 2.0 client ID:</p>
               <figure src="images/en_US/googledrive-repository-setup-3.PNG" alt="googledrive
create oauth client" width="80%"/>
@@ -1738,7 +1738,7 @@ curl -XGET http://localhost:9200/index/_
               <figure src="images/en_US/googledrive-repository-setup-4.PNG" alt="googledrive
create client id" width="80%"/>
-              <p>Afterwards we're presented with our Client ID and Client secrets needed
for the connector(where the red boxes are):</p>
+              <p>Afterwards the connector requests our Client ID and Client secrets
(where the red boxes are):</p>
               <figure src="images/en_US/googledrive-repository-setup-5.PNG" alt="googledrive
client id and secret" width="80%"/>
@@ -1747,9 +1747,9 @@ curl -XGET http://localhost:9200/index/_
                 For completeness, we present the needed steps below since they require some
manual work.</p>
-                  <li> Browse to here:;state=%2Fprofile&amp;redirect_uri=https%3A%2F%2Flocalhost&amp;response_type=code&amp;client_id=CLIENT_ID&amp;approval_prompt=force&amp;access_type=offline</li>
-                  <li> This returns a link (after acceptance) https://localhost/?state=/profile&amp;code=CODE</li>
-                  <li> Perform a POST: 
with the following as the body: grant_type=authorization_code&amp;redirect_uri=https%3A%2F%2Flocalhost&amp;client_secret=CLIENT_SECRET&amp;client_id=CLIENT_ID&amp;code=CODE</li>
+                  <li>Browse to here:;state=%2Fprofile&amp;redirect_uri=https%3A%2F%2Flocalhost&amp;response_type=code&amp;client_id=&lt;CLIENT_ID&gt;&amp;approval_prompt=force&amp;access_type=offline</li>
+                  <li>This returns a link (after acceptance), where a code is embedded
in the URL: https://localhost/?state=/profile&amp;code=&lt;CODE&gt;</li>
+                  <li>Use a tool like <em>curl</em> (<a href=""></a>)
to perform a POST to "", using the body: grant_type=authorization_code&amp;redirect_uri=https%3A%2F%2Flocalhost&amp;client_secret=&lt;CLIENT_SECRET&gt;&amp;client_id=&lt;CLIENT_ID&gt;&amp;code=&lt;CODE&gt;</li>
               <li> The response is then a json response which contains the refresh_token.</li>

View raw message