Full implementation of Docker registry scope (JWT authentication)
As I'm using GitLab to provide JWT authentication tokens to use as bearer token when using the docker registry API, I want to have a full implementation of the Docker registry scope so that it is possible to use all features of the Docker registry API without getting an
Expand the scope configuration currently available in Gitlab. Check out the Docker docs for more information about the allowed scopes in the Docker registry: https://docs.docker.com/registry/spec/auth/scope/#resource-actions
Links / references
What is it?
Expansion of the current scope implementation.
Why should someone use this feature?
The Docker registry is only manageable using the API. To allow the usage of all enhances features, you need a more complete implementation of the scope to prevent issues like an
What is the underlying (business) problem?
At the moment, it isn't possible to manage the registry itself because of the missing scopes in GitLab (GitLab will returns a 500 error when trying).
How do you use this feature?
Everyone who's using the GitLab JWT authentication in conjunction with Docker registry and wanting to use the more enhanced feature of the Docker registry API.