[sentry-junior]

Stacks on #130140. Adds the service account details page and token management to Settings.

• Each name in the service accounts list now links to /settings/:orgId/service-accounts/:serviceAccountId/. The page loads the account from the existing detail endpoint and shows its permissions, project access and created date. Editing or deleting the account is out of scope here.
• The Tokens section lists active tokens with a masked preview (sntrym_************abcd), a scopes summary, the created date, the last used date ("Never" when null), and the expiration date ("Never" when null, with an Expired tag once it has passed). Each row has a Revoke button with a confirm step. After a revoke, the list refetches.
• New Token goes to .../tokens/new/. The form has a required name and the same searchable permission scope multi-select as the create service account form, limited to the account's own scopes and all selected by default.
• The form also has an Expiration select: 30 days (default), 60 days, 90 days, a custom date, or no expiration. Picking no expiration shows a warning. A custom date must be after today, and the token works through the end of that day in the user's timezone. The form sends expiresAt as an ISO timestamp, or null for no expiration.
• After the create succeeds, the plaintext token appears once in the existing displayNewToken modal (copy input plus a "won't be shown again" warning), and closing the modal returns to the details page. Field errors in the response's detail object (name, scopes, expiresAt) show on their fields. A string detail shows as a toast.
• New Token and Revoke are disabled without service_account:write. The tooltip matches the list page's create button.
• Adds the two token routes to controlsiloUrlPatterns.ts so the frontend sends them to the control silo.

Depends on the backend token endpoint PRs, one per endpoint and stacked on #130456: list #130483, create #130507 and revoke #130508. Without them, these pages work only against mocks. The two token URLs added to knownSentryApiUrls.generated.ts here match those PRs' generated entries.

The backend PRs add the same two controlsiloUrlPatterns.ts lines, list in #130483 and revoke in #130508, so test_no_missing_urls passes on them. Whichever side lands second gets an identical change.

via @skaasten.

--

View Session [Sentry]

[github-actions]

No findings on the latest commit.