vantage

Files

T

mrhid6 e5363a64ee fix(server): per-org settings and ESO read token

The settings collection was a single global document, so every org
shared one SMTP config, alert config, retention policy and ESO read
token. GetSecretGroupDecryptedAny then flattened every org's secrets
for a group into one map, meaning any tenant's token read every
tenant's secrets.

- settings gains org_id; GetSettings/SaveSettings/RotateSecretsReadToken/
  GetWorkflowLogRetentionDays all take orgID
- VerifySecretsReadToken replaced by ResolveSecretsReadToken, which
  resolves the org from the presented token's hash; the ESO endpoint
  derives its org from the token rather than a session, since it is
  called machine-to-machine
- GetSecretGroupDecryptedAny deleted in favour of the org-scoped variant
- settings and token-rotation routes now require owner/admin
- offline sweep and log retention resolve org per server / per run
- migration 0002 stamps the legacy settings doc with the default org

Note: /api/settings now 403s for members; the web settings page needs a
matching role check.

2026-07-22 09:35:47 +01:00

assignment.go

style(models): gofmt org_id field alignment

2026-07-21 16:24:16 +01:00

audit.go

feat(models): add org/user/org_oidc models and org_id on scoped collections

2026-07-21 16:23:14 +01:00

channel.go

feat(models): add org/user/org_oidc models and org_id on scoped collections

2026-07-21 16:23:14 +01:00

console_session.go

feat: harden console sessions + complete protocol support