Browse code

Remove response modification sections from authorization design doc

Signed-off-by: Liron Levin <liron@twistlock.com>

Liron Levin authored on 2016/05/03 04:19:23
Showing 1 changed files
... ...
@@ -195,17 +195,10 @@ should implement the following two methods:
195 195
 {
196 196
    "Allow":              "Determined whether the user is allowed or not",
197 197
    "Msg":                "The authorization message",
198
-   "Err":                "The error message if things go wrong",
199
-   "ModifiedBody":       "Byte array containing a modified body of the raw HTTP body (or null if no changes required)",
200
-   "ModifiedHeader":     "Byte array containing a modified header of the HTTP response (or null if no changes required)",
201
-   "ModifiedStatusCode": "int containing the modified version of the status code (or 0 if not change is required)"
198
+   "Err":                "The error message if things go wrong"
202 199
 }
203 200
 ```
204 201
 
205
-The modified response enables the authorization plugin to manipulate the content
206
-of the HTTP response. In case of more than one plugin, each subsequent plugin
207
-receives a response (optionally) modified by a previous plugin.
208
-
209 202
 ### Request authorization
210 203
 
211 204
 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.