Skip to content

Clarify expired token UI usage

Filip Aleksic requested to merge faleksic-master-patch-74473 into master
  • Please check this box if this contribution uses AI-generated content as outlined in the GitLab DCO & CLA.

What does this MR do?

Clarifies how the UI works when it comes to expired tokens. Tokens are removed from the UI as part of gitlab-foss!12866 (merged), and when they become inactive we get into a situation where the token exists, meaning the API will return it:

HTTP GET https://gitlab.com/api/v4/groups/ID/access_tokens

[
  {
    "id": 123456,
    "name": "example-token",
    "revoked": false,
    "created_at": "2023-04-12T00:00:11.056Z",
    "scopes": [
      "read_api",
    ],
    "user_id": 123456789,
    "last_used_at": "2024-05-13T21:22:24.714Z",
    "active": false,
    "expires_at": "2024-05-14",
    "access_level": 20
  }
]

However the UI will not show it.

Related issues

gitlab-foss#19629 (closed)

Author's checklist

If you are a GitLab team member and only adding documentation, do not add any of the following labels:

  • ~"frontend"
  • ~"backend"
  • ~"type::bug"
  • ~"database"

These labels cause the MR to be added to code verification QA issues.

Reviewer's checklist

Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.

If you aren't sure which tech writer to ask, use roulette or ask in the #docs Slack channel.

  • If the content requires it, ensure the information is reviewed by a subject matter expert.
  • Technical writer review items:
    • Ensure docs metadata is present and up-to-date.
    • Ensure the appropriate labels are added to this MR.
    • Ensure a release milestone is set.
    • If relevant to this MR, ensure content topic type principles are in use, including:
      • The headings should be something you'd do a Google search for. Instead of Default behavior, say something like Default behavior when you close an issue.
      • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure GDK.
      • Any task steps should be written as a numbered list.
      • If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
  • Review by assigned maintainer, who can always request/require the reviews above. Maintainer's review can occur before or after a technical writer review.

Merge request reports