Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,761
    • Issues 44,761
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,332
    • Merge requests 1,332
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #240897
Closed
Open
Issue created Aug 24, 2020 by Henning@henning.cash

Use Deploy tokens to grant access to the Composer registry

Context

You use the GitLab Composer repository to publish and download your Composer dependencies to your private project. You can authenticate with a personal access token or a job token.

Problem to solve

The problem is that personal access tokens and job tokens are tied to a specific user. When you want to finalize your production workflows, you'd like to use a deploy token, which is not tied to a specific user or their permissions.

Proposal

Update the permissions model for group deploy tokens to allow for publishing and downloading of Composer dependencies using the write_package_registry and read_package_registry scope respectively.

Edited Dec 14, 2021 by Tim Rizzi
Assignee
Assign to
Time tracking