Skip to content

Admin Token API: Identify Pipeline trigger tokens

  • Please check this box if this contribution uses AI-generated content (including content generated by GitLab Duo features) as outlined in the GitLab DCO & CLA. As a benefit of being a GitLab Community Contributor, you can request access to GitLab Duo.

What does this MR do and why?

This MR adds support for identifying pipeline trigger tokens to the Admin Token API.

🛠️ with ❤️ at Siemens

References

MR acceptance checklist

MR Checklist ( @nwittstruck)

How to set up and validate locally

  1. Enable feature flag via rails c:
Feature.enable(:admin_agnostic_token_finder)
  1. You'll need to create a personal access token to access the token and the runner authentication token that you'd like to query:
    1. Create a personal access token with admin_mode and api capabilities. Preferences > Access Tokens > Add a new token
    2. Create a new pipeline trigger token to query. Project > Settings > CI / CD > Pipeline trigger tokens > Add new token
  2. Now you can retrieve information about this token:
curl -k --request POST \
--url 'https://gdk.test:3443/api/v4/admin/token' \
--header 'Authorization: Bearer <Admin Token from Step 2.1>' \
--header 'Content-Type: application/json' \
--data '{"token": "glptt-token-from-step-2.2"}'
{
	"id": 1,
	"token": "glptt-abc",
	"description": "example",
	"created_at": "2024-11-27T14:18:29.113Z",
	"updated_at": "2024-11-27T14:18:29.113Z",
	"last_used": null,
	"owner": {
	}
}

Related to #506554 (closed)

Edited by Nicholas Wittstruck

Merge request reports

Loading