You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/extend/plugins_authorization.md
+1-8Lines changed: 1 addition & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -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.
0 commit comments