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>

1 files changed, 1 insertions, 8 deletions

diff --git a/docs/extend/plugins_authorization.md b/docs/extend/plugins_authorization.md
index 31a6a072ab..8a1352c6d2 100644
--- a/docs/extend/plugins_authorization.md
+++ b/docs/extend/plugins_authorization.md
@@ -190,17 +190,10 @@ should implement the following two methods:
 {
    "Allow":              "Determined whether the user is allowed or not",
    "Msg":                "The authorization message",
-   "Err":                "The error message if things go wrong",
-   "ModifiedBody":       "Byte array containing a modified body of the raw HTTP body (or nil if no changes required)",
-   "ModifiedHeader":     "Byte array containing a modified header of the HTTP response (or nil if no changes required)",
-   "ModifiedStatusCode": "int containing the modified version of the status code (or 0 if not change is required)"
+   "Err":                "The error message if things go wrong"
 }
 ```
 
-The modified response enables the authorization plugin to manipulate the content
-of the HTTP response. In case of more than one plugin, each subsequent plugin
-receives a response (optionally) modified by a previous plugin.
-
 ### Request authorization
 
 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.