Browse code

Remove response modification sections from authorization design doc

Signed-off-by: Liron Levin <liron@twistlock.com>
(cherry picked from commit 638096431a36435aae0e30b6c76c134a4728ed5d)
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>

Liron Levin authored on 2016/05/03 04:19:23
Showing 1 changed files
... ...
@@ -190,17 +190,10 @@ should implement the following two methods:
190 190
 {
191 191
    "Allow":              "Determined whether the user is allowed or not",
192 192
    "Msg":                "The authorization message",
193
-   "Err":                "The error message if things go wrong",
194
-   "ModifiedBody":       "Byte array containing a modified body of the raw HTTP body (or nil if no changes required)",
195
-   "ModifiedHeader":     "Byte array containing a modified header of the HTTP response (or nil if no changes required)",
196
-   "ModifiedStatusCode": "int containing the modified version of the status code (or 0 if not change is required)"
193
+   "Err":                "The error message if things go wrong"
197 194
 }
198 195
 ```
199 196
 
200
-The modified response enables the authorization plugin to manipulate the content
201
-of the HTTP response. In case of more than one plugin, each subsequent plugin
202
-receives a response (optionally) modified by a previous plugin.
203
-
204 197
 ### Request authorization
205 198
 
206 199
 Each plugin must support two request authorization messages formats, one from the daemon to the plugin and then from the plugin to the daemon. The tables below detail the content expected in each message.