Frontend UI for managing the generic personal access tokens backed by mammon #80. Lets a logged-in user mint a token, copy the one-time secret, see their existing tokens (metadata only), and revoke them. Tokens are general-purpose (usable for MCP and any other programmatic access), not MCP-specific.
Scope
A settings/account view listing the user's personal access tokens (label, created, last-used?, expiry) via the generated mammon client.
Create flow: prompt for a label (+ optional expiry), then surface the raw secret exactly once with a copy control and a clear "you won't see this again" warning.
Revoke action per token with confirmation.
Wire through the existing auth/session store; no direct ESI calls.
Explicitly out of scope
Backend token store and endpoints (mammon #80).
/mcp authentication (mammon #81).
Acceptance criteria
User can create a token and copy the secret once; it is not retrievable afterward.
User can list and revoke their tokens; the secret is never displayed in the list.
UI uses the regenerated mammon client (no hand-rolled endpoints).
Test coverage per project conventions.
Related
Depends on mammon #80 (endpoints + regenerated OpenAPI client). Related consumer: mammon #81 (/mcp auth).
## Summary
Frontend UI for managing the generic personal access tokens backed by `mammon #80`. Lets a logged-in user mint a token, copy the one-time secret, see their existing tokens (metadata only), and revoke them. Tokens are general-purpose (usable for MCP and any other programmatic access), not MCP-specific.
## Scope
- A settings/account view listing the user's personal access tokens (label, created, last-used?, expiry) via the generated mammon client.
- Create flow: prompt for a label (+ optional expiry), then surface the raw secret exactly once with a copy control and a clear "you won't see this again" warning.
- Revoke action per token with confirmation.
- Wire through the existing auth/session store; no direct ESI calls.
## Explicitly out of scope
- Backend token store and endpoints (`mammon #80`).
- `/mcp` authentication (`mammon #81`).
## Acceptance criteria
- [ ] User can create a token and copy the secret once; it is not retrievable afterward.
- [ ] User can list and revoke their tokens; the secret is never displayed in the list.
- [ ] UI uses the regenerated mammon client (no hand-rolled endpoints).
- [ ] Test coverage per project conventions.
## Related
Depends on `mammon #80` (endpoints + regenerated OpenAPI client). Related consumer: `mammon #81` (`/mcp` auth).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Frontend UI for managing the generic personal access tokens backed by
mammon #80. Lets a logged-in user mint a token, copy the one-time secret, see their existing tokens (metadata only), and revoke them. Tokens are general-purpose (usable for MCP and any other programmatic access), not MCP-specific.Scope
Explicitly out of scope
mammon #80)./mcpauthentication (mammon #81).Acceptance criteria
Related
Depends on
mammon #80(endpoints + regenerated OpenAPI client). Related consumer:mammon #81(/mcpauth).MCP token management UI: create, list, revoketo Personal access token management UI: create, list, revoke