Liron Levin 3c157713b3 Extend Docker authorization with TLS user information ... Currently Docker authorization framework does not use any user information, which already available in the Docker context for TLS connection. The purpose of this CR is to complete the existing authz work by adding the basic client certificate details (SUBJECT_NAME) and authentication method (TLS) to the authz request. We think this should be the default behavior when no extended authorization module is specified (currently WIP under #20883). Signed-off-by: Liron Levin <liron@twistlock.com>		2016-03-27 15:53:55 +03:00
..
authorization.go	Extend Docker authorization with TLS user information	2016-03-27 15:53:55 +03:00
cors.go
debug.go	api: server: server: remove redunant debugf	2016-03-07 09:03:29 +01:00
middleware.go
user_agent.go	Pass upstream client's user agent through to registry on image pulls	2016-03-20 04:30:09 -07:00
version.go
version_test.go