Project Access Token creation failing (false positive)

Summary

I'm trying to create a recently released Project access token https://docs.gitlab.com/ee/user/project/settings/project_access_tokens.html, and I get a "Your new project access token has been created." but it does not work.

I have owner permissions on the Project, and I'm o GitLab.com I also tried calling an API using this token (https://gitlab.com/api/v4/projects/18860192/statistics), but it failed.

Steps to reproduce

• Open Project Access Token page
• Give the new token a name, expiration and scope (I tried many combinations, all gave the same output)
• Click on "Create Project Access Token"
• The new token appears to me at the top, but not on the list at the bottom.
• Refresh the screen, it doesn't show the created token in the list as a "Active project access tokens"
• Navigate to the members of the group and search for the "Token Name" or "bot", it doesn't find any user as stated in the documentation

Example Project

https://gitlab.com/bendigobank/projecttemplates/nodejs

What is the current bug behavior?

Token is "created" but can't be seen as active or used to call this project's APIs

What is the expected correct behavior?

Token is "created", listed as active and used to call this project's APIs

Relevant logs and/or screenshots

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info

Results of GitLab application Check

Expand for output related to the GitLab application check

Possible fixes

added customer typebug + 1 deleted label

Setting label(s) devopsmanage ~"group::access" sectiondev based on ~"Category:Authentication and Authorization" ~"group::access".

added devopsmanage groupauthentication and authorization [DEPRECATED] sectiondev labels

Enterprise Gold Customer considered this bug as high priority. cc @mushakov please take a look to see if when this issue can be addressed. Thanks!

@bma This issue appears to be a duplicate of #271635 (closed) . Could your customer try again?

mentioned in issue gitlab-org/quality/triage-reports#791 (closed)

mentioned in issue gitlab-org/quality/triage-reports#875 (closed)

mentioned in issue gitlab-org/quality/triage-reports#974 (closed)

mentioned in issue gitlab-org/quality/triage-reports#1051 (closed)

mentioned in issue gitlab-org/quality/triage-reports#1105 (closed)

mentioned in issue gitlab-org/quality/triage-reports#1198 (closed)

mentioned in issue gitlab-org/quality/triage-reports#1273 (closed)

mentioned in issue gitlab-org/quality/triage-reports#1369 (closed)

mentioned in issue gitlab-org/quality/triage-reports#1436 (closed)

mentioned in issue gitlab-org/quality/triage-reports#1527 (closed)

mentioned in issue gitlab-org/quality/triage-reports#1600 (closed)

mentioned in issue gitlab-org/quality/triage-reports#1689 (closed)

mentioned in issue gitlab-org/quality/triage-reports#1778 (closed)

mentioned in issue gitlab-org/quality/triage-reports#1888 (closed)

mentioned in issue gitlab-org/quality/triage-reports#1990 (closed)

mentioned in issue gitlab-org/quality/triage-reports#2051 (closed)

mentioned in issue gitlab-org/quality/triage-reports#2147 (closed)

mentioned in issue gitlab-org/quality/triage-reports#2255 (closed)

mentioned in issue gitlab-org/quality/triage-reports#2334 (closed)

mentioned in issue gitlab-org/quality/triage-reports#2408 (closed)

mentioned in issue gitlab-org/quality/triage-reports#2504 (closed)

mentioned in issue gitlab-org/quality/triage-reports#2574 (closed)

added vintage label

closed