Guest24897
/
DockerCLI
mirror of https://github.com/docker/cli.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Remove response modification sections from authorization design doc 

Signed-off-by: Liron Levin <liron@twistlock.com>
This commit is contained in:
Liron Levin 2016-05-02 22:19:23 +03:00 committed by Tibor Vass
parent 8b38343e46
commit 3e48f4b4ab
1 changed files with 1 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/extend/plugins_authorization.md
View File

@ -195,17 +195,10 @@ should implement the following two methods:
{ {
"Allow": "Determined whether the user is allowed or not", "Allow": "Determined whether the user is allowed or not",
"Msg": "The authorization message", "Msg": "The authorization message",
"Err": "The error message if things go wrong", "Err": "The error message if things go wrong"
"ModifiedBody": "Byte array containing a modified body of the raw HTTP body (or null if no changes required)",
"ModifiedHeader": "Byte array containing a modified header of the HTTP response (or null if no changes required)",
"ModifiedStatusCode": "int containing the modified version of the status code (or 0 if not change is required)"
} }
``` ```
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 ### 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. 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.