-
- Downloads
There was a problem fetching the pipeline summary.
Create read_registry scope with JWT auth
This is the first commit doing mainly 3 things: 1. create a new scope and allow users to use it 2. Have the JWTController respond correctly on this 3. Updates documentation to suggest usage of PATs There is one gotcha, there will be no support for impersonation tokens, as this seems not needed. Fixes gitlab-org/gitlab-ce#19219
parent
a8901ce6
No related branches found
No related tags found
Pipeline #
Showing
- app/controllers/jwt_controller.rb 5 additions, 3 deletionsapp/controllers/jwt_controller.rb
- app/controllers/profiles/personal_access_tokens_controller.rb 1 addition, 1 deletion...controllers/profiles/personal_access_tokens_controller.rb
- app/models/personal_access_token.rb 5 additions, 6 deletionsapp/models/personal_access_token.rb
- changelogs/unreleased/zj-read-registry-pat.yml 4 additions, 0 deletionschangelogs/unreleased/zj-read-registry-pat.yml
- doc/user/project/container_registry.md 7 additions, 6 deletionsdoc/user/project/container_registry.md
- lib/gitlab/auth.rb 28 additions, 14 deletionslib/gitlab/auth.rb
- lib/gitlab/auth/result.rb 4 additions, 0 deletionslib/gitlab/auth/result.rb
- spec/lib/gitlab/auth_spec.rb 7 additions, 0 deletionsspec/lib/gitlab/auth_spec.rb
- spec/models/personal_access_token_spec.rb 18 additions, 2 deletionsspec/models/personal_access_token_spec.rb
- spec/requests/jwt_controller_spec.rb 14 additions, 1 deletionspec/requests/jwt_controller_spec.rb