Lisca Ana-Roberta 336526065f feat(groups)!: added "groups" mechanism for authZ (#1123) ... BREAKING CHANGE: repository paths are now specified under a new config key called "repositories" under "accessControl" section in order to handle "groups" feature. Previously the repository paths were specified directly under "accessControl". This PR adds the ability to create groups of users which can be used for authZ policies, instead of just users. { "http": { "accessControl": { "groups": { Just like the users, groups can be part of repository policies/default policies/admin policies. The 'groups' field in accessControl can be missing if there are no groups. The permissions priority is user>group>default>admin policy, verified in this order (in authz.go), and permissions are cumulative. It works with LDAP too, and the group attribute name is configurable. The DN of the group is used as the group name and the functionality is the same. All groups for the given user are added to the context in authn.go. Repository paths are now specified under a new keyword called "repositories" under "accessControl" section in order to handle "groups" feature. Signed-off-by: Ana-Roberta Lisca <ana.kagome@yahoo.com>		2023-03-08 11:47:15 -08:00
..
checkrepo.go	feat(repodb): Implement RepoDB for image specific information using boltdb/dynamodb (#979)	2023-01-09 12:37:44 -08:00
context.go	feat(groups)!: added "groups" mechanism for authZ (#1123)	2023-03-08 11:47:15 -08:00