Files
agent-estate-wiki/infrastructure/credentials-map.md
T
Hermes 341dda95dd stocktake 2026-11-11: 36 stale pages re-verified (0 stale); fallback chain rewritten 4/6 slots; CT333 'clawtest' naming claim corrected; nous 404 credits signature replaces refresh-token 401; estate shrank (VM 310 + CT601 gone)
- freshness: 36 stale / 93 fresh / 3 no-date -> 0 stale / 129 fresh / 3 no-date of 132 (same-day report regenerated after the corrections, per pattern 13)
- skills: 299 skills / 67 categories (count unchanged; generator arithmetic re-verified by hand against the live tree: 300 SKILL.md files - 1 nested duplicate = 299)
- runbooks/test-openrouter: live fallback chain rewritten (primary back to smart-route/custom:omni-101; mimo-v2.5, stepfun, qwen3.5/ollama-cloud out; guacano + kilo-reflection-beam-free in); ollama.com dropped from the URL test list; guacano/litellm noted as internal + key-gated
- comparisons/hermes-vs-nanobot: the 2026-10-20 'CT333 is zeroclaw in Proxmox naming' claim was itself wrong - pct list and hostname both return clawtest
- incidents/2026-10-22-nous: refresh-token failure gone from logs; new signature 404 insufficient_credits_for_paid_model from auxiliary.pulse_memory (ninth slot, back on nous, paid model) - open item revised
- incidents/2026-08-29-gmail: email crons now ok but root cause unfixed 74 days (himalaya message read still in fetch_newsletters.py; goimapnotify back up PID 441; monitor still paused)
- 30 further pages re-verified live and de-flagged with dated probe notes (ct207 ingress, CT205 guanaco v0.8.15, CT270 nextcloud 33.0.2.2, headless stack, hermes-ui both hosts, systemd units + cgroup limits, terminal/tool_search/mnemosyne/custom_providers config blocks, ops profile still deleted, hosts/pve guest lists)
- log.md addendum + index.md date bump; no page deleted, no secrets written
2026-11-11 03:52:48 +08:00

65 lines
3.2 KiB
Markdown

---
title: Credentials Map
type: infrastructure
status: active
created: 2026-07-22
updated: 2026-11-11
verified_on: 2026-11-11
confidence: medium
tags: [credentials, security, infrastructure]
sources: []
---
# Credentials Map
## Purpose
Document where credentials are stored and what service they belong to.
**No credential values are stored in this wiki.**
## Storage Locations
| Service | Credential Store | Location | Notes |
|---|---|---|---|
| Telegram Bot | Hermes config | `~/.hermes/config.yaml` | Not exposed in wiki |
| Discord Bot | Hermes config | `~/.hermes/config.yaml` | Not exposed in wiki |
| Email | Hermes config | `~/.hermes/config.yaml` |-connected via IMAP/SMTP |
| Mattermost | Hermes config | `~/.hermes/config.yaml` | Connected |
| CF Access (mcp-portal) | Hermes config | `~/.hermes/config.yaml` | Client ID + Secret |
| LiteLLM | Hermes config | `~/.hermes/config.yaml` | API key |
| OmniRoute | Hermes config | `~/.hermes/config.yaml` | API key |
| Anthropic | Hermes config/OAuth | `~/.hermes/` | `.anthropic_oauth.json` |
| API Vault | Hermes vault | via `hermes-api-vault` skill | Notion-backed vault |
| Huawei Cloud | Terraform state / config | Unverified | |
| GitHub | Hermes config / gh CLI | `~/.config/gh/` or `~/.hermes/` | Unverified |
> **Re-verified 2026-10-20 — two corrections to the table above.**
> 1. **Email credentials live in `~/.hermes/.env`, not `config.yaml`.** `config.yaml` has **no**
> `imap`/`smtp`/`email` keys; the live variables are `EMAIL_ADDRESS`, `EMAIL_IMAP_HOST`,
> `EMAIL_SMTP_HOST`, `EMAIL_ALLOWED_USERS`, `EMAIL_HOME_ADDRESS`, `EMAIL_ALLOW_ALL_USERS`
> and friends in `~/.hermes/.env` (mode `0600`). The `config.yaml` row is wrong — point at the `.env`.
> 2. **The `tools:` block in `config.yaml` contains only `tool_search`.** There are no `gmail`,
> `discord`, `mattermost` or `email` tool sections there. Discord and Telegram appear as
> **top-level** `discord:` / `telegram:` blocks, and Mattermost is a **plugin**
> (`platforms/mattermost`), not a `tools:` entry. So the "Hermes config" location column is right
> for those, but the implication that they are `tools:` sections is not.
> No `connectors:` block is configured in `config.yaml` at all.
> `~/.hermes/auth.json` also exists and holds OAuth tokens — treat as a credential store.
> **Re-verified 2026-11-11 — both 2026-10-20 corrections still hold.** `config.yaml` still has **no**
> `imap`/`smtp`/`email`/`connectors`/`gmail`/`mattermost` keys; the email credentials still live in
> `~/.hermes/.env` (mode `0600`, keys `EMAIL_ADDRESS`, `EMAIL_IMAP_HOST`, `EMAIL_SMTP_HOST`,
> `EMAIL_ALLOWED_USERS`, `EMAIL_HOME_ADDRESS`, `EMAIL_ALLOW_ALL_USERS`, `EMAIL_POLL_INTERVAL` and
> more). `tools:` still contains only `tool_search`. `discord:` and `telegram:` are top-level
> blocks, and `platforms:` still lists `mattermost` (so Mattermost remains a plugin, not a `tools:`
> entry). `~/.hermes/auth.json` exists and holds OAuth material.
## Rules
- Credentials never written to this wiki
- API vault is first-stop for any key lookup
- If vault lacks it, surface the gap to user — do not fabricate
## Related
- [[hosts]]
- [[model-providers]]
- [[messaging-integrations]]