6 Commits

Author	SHA1	Message	Date
Sebastiaan van Stijn	6a9f7c543c	pkg/authorization: remove // import comments ... These comments were added to enforce using the correct import path for our packages ("github.com/docker/docker", not "github.com/moby/moby"). However, when working in go module mode (not GOPATH / vendor), they have no effect, so their impact is limited. Remove these imports in preparation of migrating our code to become an actual go module. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>	2025-05-30 15:59:17 +02:00
Daniel Nephin	4f0d95fa6e	Add canonical import comment ... Signed-off-by: Daniel Nephin <dnephin@docker.com>	2018-02-05 16:51:57 -05:00
Diego Romero	48b8f54876	Fixed a typo within pkg/authorization/api.go ... Signed-off-by: Diego Romero <idiegoromero@gmail.com>	2017-01-17 21:51:16 -05:00
Antonio Murdaca	1452c1cc71	pkg/authorization: send request's TLS peer certificates to plugins ... Signed-off-by: Antonio Murdaca <runcom@redhat.com>	2016-10-31 17:37:19 +01:00
Antonio Murdaca	46e3a249a1	pkg: authorization: add Err to tweak response status code ... Signed-off-by: Antonio Murdaca <runcom@redhat.com>	2015-12-17 11:08:47 +01:00
Liron Levin	75c353f0ad	Docker authorization plug-in infrastructure enables extending the functionality of the Docker daemon with respect to user authorization. The infrastructure enables registering a set of external authorization plug-in. Each plug-in receives information about the user and the request and decides whether to allow or deny the request. Only in case all plug-ins allow accessing the resource the access is granted. ... Each plug-in operates as a separate service, and registers with Docker through general (plug-ins API) [https://blog.docker.com/2015/06/extending-docker-with-plugins/]. No Docker daemon recompilation is required in order to add / remove an authentication plug-in. Each plug-in is notified twice for each operation: 1) before the operation is performed and, 2) before the response is returned to the client. The plug-ins can modify the response that is returned to the client. The authorization depends on the authorization effort that takes place in parallel [https://github.com/docker/docker/issues/13697]. This is the official issue of the authorization effort: https://github.com/docker/docker/issues/14674 (Here)[https://github.com/rhatdan/docker-rbac] you can find an open document that discusses a default RBAC plug-in for Docker. Signed-off-by: Liron Levin <liron@twistlock.com> Added container create flow test and extended the verification for ps	2015-12-08 17:34:15 +02:00