Skip to content

Remove programmatic access to registration tokens

What does this MR do?

In https://gitlab.com/gitlab-org/gitlab/-/issues/326018, we have discovered an issue where instance registration tokens were shown incorrectly to instance admins on groups CI/CD settings.

This did not show any information that users didn't already have access to, but it did reveal the security risk posed by programmatic access to registration tokens. A similar mistake that would show an instance token to everyone is a very real risk with huge implications.

So let's prevent this from happening by removing programmatic access to those tokens. The installation instructions work just as well if the token is not prefilled and has a placeholder like <paste your registration token here> instead.

A further ~"technical debt" issue has been opened in #326102 (closed) to cleanup those methods and remove the unnecessary code. Removing the security risk is the priority of this MR and cleanup can be handled at a lower priority level.

Screenshots (strongly suggested)

Screenshot_2021-03-26_at_13.19.01

Does this MR meet the acceptance criteria?

Conformity

Availability and Testing

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

  • Label as security and @ mention @gitlab-com/gl-security/appsec
  • The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
  • Security reports checked/validated by a reviewer from the AppSec team
Edited by Lucas Charles

Merge request reports

Loading