Add ability to view and manage api keys via the frontend

[collectoss-issue-migrator]

Note

Migrated from augurlabs/augur#3041
Originally opened by @ABrain7710 on 2025-03-05

---

• Add "Worker Oauth Keys" section to the admin dashboard

  • Display keys in a table
  • Use the same table layout and formatting that is used for current frontend tables (IE: pagination, common theme, etc...)
  • Make table filterable and sortable by each column
  • Only display relevant columns: Key ID, Key platform, Token (hidden by default, click to show)
  • Add delete button (with confirmation) to remove a key from the worker_oauth table and unpublish from the key orchestrator

• Display invalid keys in a table separately from the rest, with the same formatting as the primary table

  • Keys must be gathered from the KeyPublisher interface, and joined on the data from the worker_oauth table in order to determine the IDs of the invalid keys at runtime.
  • Additionally, any keys in the worker_oauth table that were not loaded into the key orchestrator interface at startup are also considered invalid.

• All requisite endpoints must be protected with @admin_required

• Add form to insert new keys

  1. Add new keys to worker_oauth table
  2. Check that the provided key is valid before inserting (via is_bad_api_key() in GithubApiKeyHandler or GitlabApiKeyHandler)
  3. Publish new keys with the KeyPublisher so they are available for new collection requests

Prerequisites

The admin dashboard is being implemented in the admin-changes branch. All changes to the dashboard must be based on this branch.

This issue is dependent upon the merging of augurlabs/augur#3058, as that adds the INVALIDATE commands to the orchestration API and the KeyClient.

[collectoss-issue-migrator]

Note

Migrated comment from original
Originally posted by @demoncoder-crypto on 2025-03-09

---

I tried to work on this issue. let me if anything else is needed

[collectoss-issue-migrator]

Note

Migrated comment from original
Originally posted by @Ulincsys on 2025-03-18

---

This issue was originally a backlog item that we had intended on working towards at a later date.

However, since it has drawn much attention over the past week, I've added the specific requirements for a full implementation of the interface.

[collectoss-issue-migrator]

Note

Migrated comment from original
Originally posted by @officialasishkumar on 2025-03-20

---

should i create a new branch on top of admin-changes branch and put my work there?

cc: @Ulincsys

[collectoss-issue-migrator]

Note

Migrated comment from original
Originally posted by @Ulincsys on 2025-03-21

---

@officialasishkumar You can rebase off of dev, or make a new branch.

Or, we will be pulling dev up to speed with main as soon as augurlabs/augur#3077 gets merged, then your branch will be able to be merged with dev without creating a conflict and without the need to rebase.

[MoralCode]

#411 might address this