Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #990

Closed
Open
Created Jun 27, 2012 by Administrator@rootOwner

User ssh keys linked to projects

Created by: Pratima

As a user when I remove my ssh key and add a new my ssh key, I lose read/write access to the projects that were created when I was using the older key. Essentially it should not matter what my ssh key is as far as I have the private key on my machine to authenticate it with. I should still have access to my repos irrespective of when they were created as far as my keys can talk to each other. In the keys model we see a key belonging to a project. I can;t understand why a key should belong to a project. Its strictly a user related object. As far as the user has the private part he/she should be able to write to his/her projects. Th project should not dictate which key should be used in case of multiple keys or change of keys.

Assignee
Assign to
Time tracking