New Project Access Tokens do not show in "Active project access tokens"
Summary
A user has attempted to create a Project Access Token with the write_repository scope. Once the "Create Access Token" button has been clicked, the token is displayed to the user but it never appears under Active project access tokens. When checking Kibana, it looks like params are passed and the request to create a token is received, there are no exceptions otherwise. The user creating the PAT is an Owner of the project and another Owner of the same project experienced the same behavior. It seems like it may be specific to this namespace.
The user attempted to use the token despite it not showing as active, and the projects endpoint shows a 404, but other endpoints such as the user endpoint does not. "error":"insufficient_scope" should be returned if the problem was scope, otherwise it would return results.
Additional Notes
- It's unclear if this actually impacts how the token works.
- Not being able to see whether a token exists is definitely problematic especially if you can't expire them for security purposes
Steps to reproduce
Unable to reproduce in a a test project. However, please see customer ticket for example namespace.
Example Project
Please see ZD Ticket: https://gitlab.zendesk.com/agent/tickets/177618
What is the current bug behavior?
A newly created Project Access Token does not show up in Active project access tokens. It is unclear if the token itself works properly and was scoped properly.
What is the expected correct behavior?
A newly created Project Access Token should show up in Active project access tokens and work for the selected scope.
Relevant logs and/or screenshots
https://log.gprd.gitlab.net/goto/8c31edcf13b7ba89d65b4d231dd30f79
- See video in ZD Ticket
Output of checks
This happens on GitLab.com 13.6.0-pre 675750b9