Anusha Ragunathan 38de272bd4 When authz plugin is disabled, remove from authz middleware chain. ... When the daemon is configured to run with an authorization-plugin and if the plugin is disabled, the daemon continues to send API requests to the plugin and expect it to respond. But the plugin has been disabled. As a result, all API requests are blocked. Fix this behavior by removing the disabled plugin from the authz middleware chain. Tested using riyaz/authz-no-volume-plugin and observed that after disabling the plugin, API request/response is functional. Fixes #31836 Signed-off-by: Anusha Ragunathan <anusha.ragunathan@docker.com>		2017-03-22 12:07:39 -07:00
..
v2	plugin: use pkg/errors in more places	2017-01-31 16:45:26 -08:00
backend_linux.go	When authz plugin is disabled, remove from authz middleware chain.	2017-03-22 12:07:39 -07:00
backend_unsupported.go	Use distribution reference	2017-02-07 11:08:37 -08:00
blobstore.go	*: use opencontainers/go-digest package	2017-01-06 18:48:41 -08:00
defs.go	When authz plugin is disabled, remove from authz middleware chain.	2017-03-22 12:07:39 -07:00
manager.go	When authz plugin is disabled, remove from authz middleware chain.	2017-03-22 12:07:39 -07:00
manager_linux.go	Net dial to the plugin socket during enable.	2017-02-27 18:11:28 -08:00
manager_solaris.go	Make v2/Plugin accesses safe.	2016-12-06 13:23:41 -08:00
manager_test.go	Rewrite the function 'validatePrivileges' without checking order	2017-02-04 08:47:40 +08:00
manager_windows.go	Make v2/Plugin accesses safe.	2016-12-06 13:23:41 -08:00
store.go	Use distribution reference	2017-02-07 11:08:37 -08:00
store_test.go	Implement content addressability for plugins	2016-12-23 13:29:58 -08:00