From 321f2cdf743872e4bfa671e379f3e87f78de782d Mon Sep 17 00:00:00 2001 From: Dylan William Hardison Date: Fri, 11 Sep 2015 10:23:25 -0400 Subject: rst formatting error --- docs/en/rst/integrating/auth-delegation.rst | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) (limited to 'docs/en') diff --git a/docs/en/rst/integrating/auth-delegation.rst b/docs/en/rst/integrating/auth-delegation.rst index d7557e682..403f01e2f 100644 --- a/docs/en/rst/integrating/auth-delegation.rst +++ b/docs/en/rst/integrating/auth-delegation.rst @@ -16,14 +16,14 @@ and the Bugzilla site is `http://bugs.example.org`. 1. Provide a link or redirect the user to `http://bugs.example.org/auth.cgi?callback=http://app.example.org/callback&description=app%description` 2. Assuming the user is agreeable, the following will happen: - 1. Bugzilla will issue a POST request to `http://app.example.org/callback` - with a the request body data being a JSON object with keys `client_api_key` and `client_api_login`. - 2. The callback, when responding to the POST request must return a JSON object with a key `result`. This result - is intended to be a unique token used to identify this transaction. - 3. Bugzilla will then cause the useragent to redirect (using a GET request) to `http://app.example.org/callback` - with additional query string parameters `client_api_login` and `callback_result`. - 4. At this point, the consumer now has the api key and login information. Be sure to compare the `callback_result` to whatever result was initially sent back - to Bugzilla. + 1. Bugzilla will issue a POST request to `http://app.example.org/callback` + with a the request body data being a JSON object with keys `client_api_key` and `client_api_login`. + 2. The callback, when responding to the POST request must return a JSON object with a key `result`. This result + is intended to be a unique token used to identify this transaction. + 3. Bugzilla will then cause the useragent to redirect (using a GET request) to `http://app.example.org/callback` + with additional query string parameters `client_api_login` and `callback_result`. + 4. At this point, the consumer now has the api key and login information. Be sure to compare the `callback_result` to whatever result was initially sent back + to Bugzilla. 3. Finally, you should check that the API key and login are valid, using the :ref:`rest_user_valid_login` REST resource. -- cgit v1.2.3-24-g4f1b