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
  • #270200
Closed
Open
Issue created Oct 19, 2020 by Dan Jensen@djensenContributor

Down-tier admin PAT API features to Core

Problem to solve

Admins need better PAT enforcement capability.

We introduced API endpoints that allow GitLab Ultimate admin users to read and revoke PAT credentials via the API. However, as explained in the epic, GitLab Core admin users are still in need of this functionality.

Proposal

  • Move the admin-only API functionality for PATs to GitLab Core per &4110 (comment 422306309)
  • Make these API features available to non-admin users in GitLab Core, who should be able to list and revoke their own PATs
Edited Oct 20, 2020 by Matt Gonzales (ex-GitLab)
Assignee
Assign to
Time tracking