dorfteich/packages/shared/i18n/en/apiTokens.json
Claude Fable 5 afef45732a
All checks were successful
CI / Lint, typecheck, test (pull_request) Successful in 4m52s
CI / Build container images (pull_request) Successful in 3m55s
CI / Auth e2e pack (pull_request) Successful in 7m52s
CI / Import/export fidelity gate (pull_request) Successful in 55s
CD / Build and push images (push) Successful in 16s
CD / Deploy to Test (push) Successful in 14s
CD / Smoke tests against Test (push) Successful in 1m14s
CD / Promote to Int (push) Successful in 11s
CI / Lint, typecheck, test (push) Successful in 4m55s
CI / Build container images (push) Has been skipped
CI / Auth e2e pack (push) Successful in 7m34s
CI / Import/export fidelity gate (push) Successful in 58s
#191: feeds.enabled instance switch, feed-token log masking
Chosen path: an instance master switch following the api.enabled/
mcp.enabled pattern — while off, both feed routes AND the feed-token
management answer 404 (existence hidden). Default ON: feeds predate the
switch, existing instances and their subscribed readers keep working;
the VS-NfD reference configuration (#227) turns it off. Admin UI gets
the toggle next to the API/MCP switches (i18n de+en).

Moving the token out of the query string is documented as rejected: a
path segment lands in the same proxy and request logs, and feed readers
cannot send headers — that is why the credential is in the URL at all.
What DID leak was our own request log (pino logs req.url): the req
serializer now masks ?token= values (common/mask-token-param.ts), so no
code path logs the credential.

Refs #191

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0168Ph5uBmHm8X28CSVpbpnJ
2026-07-30 11:34:43 +02:00

68 lines
3.2 KiB
JSON

{
"section": {
"title": "API tokens",
"intro": "Personal access tokens let scripts and integrations use the public API as you. A token has your permissions, narrowed by its scope and an optional pond restriction.",
"instanceDisabled": "The public API is currently disabled on this instance — tokens can be created but will not work until a Site Admin enables it.",
"empty": "No API tokens yet."
},
"fields": {
"name": "Name",
"scope": "Scope",
"scopeRead": "Read only",
"scopeWrite": "Read and write",
"expiresAt": "Expires (optional)",
"ponds": "Restrict to ponds (optional)",
"pondsHint": "No selection = every pond you can access (that has the API enabled)."
},
"list": {
"created": "Created",
"lastUsed": "Last used",
"never": "never",
"expires": "Expires",
"status": "Status",
"active": "Active",
"revoked": "Revoked",
"expired": "Expired",
"allPonds": "all ponds",
"revoke": "Revoke",
"revokeConfirm": "Revoke this token? Clients using it stop working immediately."
},
"create": {
"button": "Create token",
"pending": "Creating…",
"createdTitle": "Token created",
"createdHint": "Copy it now — it is shown only this once.",
"copy": "Copy",
"copied": "Copied."
},
"pond": {
"title": "Public API",
"label": "Expose this pond through the public API",
"hint": "Off by default. When enabled, users can reach this pond with their API tokens — with exactly the permissions they have here anyway. The instance-wide API switch must also be on.",
"saved": "Saved.",
"mcpLabel": "Expose this pond to AI assistants (MCP)",
"mcpHint": "Off by default and independent of the REST toggle. When enabled, MCP clients such as Claude Code can reach this pond with an API token — again with exactly the user's permissions. The instance-wide MCP switch must also be on."
},
"admin": {
"title": "Public API",
"label": "Enable the public REST API",
"hint": "Master switch (default off). Users then create personal access tokens in their settings; each pond additionally opts in via its pond settings. Documentation: /api/public/v1/openapi.json",
"save": "Save",
"saved": "Saved.",
"mcpLabel": "Enable the built-in MCP endpoint",
"mcpHint": "Master switch (default off), independent of the REST API. MCP clients connect to /api/mcp with an API token; each pond additionally opts in via its pond settings. See docs/self-hosting/public-api.md.",
"feedsLabel": "Enable Atom feeds",
"feedsHint": "Master switch (default on). While off, every feed URL and the feed-token management answer 404 — for hardened environments where feed tokens must not appear in URLs as read credentials."
},
"feed": {
"title": "Feed tokens",
"intro": "Read-only tokens for Atom feeds: append ?token=… to a feed URL so your feed reader can subscribe to non-public ponds and pages. They never grant API access.",
"create": "Create feed token",
"revealHint": "Copy the token now — it is only shown once.",
"urlHint": "Example feed URL: {{url}}",
"pondPlaceholder": "pond",
"empty": "No feed tokens yet.",
"delete": "Delete"
}
}