Skip to content
GitLab Next
  • Menu
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 43,792
    • Issues 43,792
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,400
    • Merge requests 1,400
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & 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.org
  • GitLabGitLab
  • Issues
  • #351759
Closed
Open
Created Feb 02, 2022 by Max Woolf@mwoolfMaintainer

Remove project access tokens from the personal access tokens list in Credentials Inventory

Overview

Currently, project access tokens appear in the "Personal Access Tokens" list in the credentials inventory. Once !79645 (merged) is merged, those tokens will appear in both lists. This is both redundant and potentially confusing.

Proposal

  • Remove all project access tokens from the credentials inventory in the "Personal Access Tokens" tab.
  • Create migration to remove all project bot users that do not have a personal access token. (This is risky and we need to decide if the potential impact is worth the risk.)

Potential Impact

Project access tokens revoked from the personal access token's tab could create a situation where bot users remain in existance without an associated access token.

Related to #243833 (closed).

Edited Feb 03, 2022 by Max Woolf
Assignee
Assign to
Time tracking