Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab GitLab
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 38,038
    • Issues 38,038
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 1,345
    • Merge requests 1,345
  • Requirements
    • Requirements
    • List
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #240897

Closed
Open
Created Aug 24, 2020 by Henning@henning.cash

Use Deploy tokens to grant access to the Composer registry

Summary

Group deploy tokens with read_package_registry scope do not grant access to the Composer Package registry.
GitLab responds with a 404 instead.

Steps to reproduce

  1. Create a group
  2. Add a project within the group and deploy a composer package to its registry
  3. Create a deploy token to the group with read_package_registry scope
  4. Use the deploy token to access the registry at /api/v4/group/<group_id>/-/packages/composer/packages.json

What is the current bug behavior?

You cannot access the packages.json. It fails with a 404 error – maybe related to #232636 (closed).
The token needs api_read access which cannot be granted.

What is the expected correct behavior?

We expect to see the packages.json of the group.

Possible fixes

Either deploy tokens need the api_read scope or the Composer Package Registry should be accessible if the read_package_registry scope was granted.

Edited Aug 31, 2020 by Tim Rizzi
Assignee
Assign to
Backlog
Milestone
Backlog
Assign milestone
Time tracking