Valistry

GitLab Duo seats

Duo seats, holders as codes, not names. The plan, and seats bought and assigned. The last day each person used Duo. Never a name, code or a prompt.

Access

Kind
Sign in on the vendor's page; nothing typed here
What to give
Group and access token
Why that one
A personal access token with read_api, from a group Owner. Valistry reads Duo seats.

What it attributes on its own

From the source
seat holder (hashed); plan; last day of Duo use; seats bought and assigned
Needs a rule or a trace
the seat price, which you enter; when each seat was assigned; the same person at other vendors; Duo use per day; GitLab Credits as cost

The addresses it calls

  • https://gitlab.com/api/graphql
  • https://gitlab.com/api/v4/personal_access_tokens/self

Valistry calls only these addresses. It blocks any other call and logs every call.

Connecting it

  1. Create a personal access token. Click Open GitLab, then Generate token → Legacy token. Open ↗