Persisted resource redaction masks the vault key inside a sensitive field ref (data name containing a vault-resolved value), so readResource fails with Secret not found

Teamz7d ago

#3581

Explicit pinned host-key policy, argv exec, atomic copy, and agent-based identityContent

Teams17d ago

#3582

dns_records lookup: distinguish no-match from API/auth/network failure (or add a list method)

Teams17d ago

#3584

kubernetes/secret: idempotent ensure method and a metadata-only get

Teams17d ago

#3580

Finer-grained method locking: a long-running method on one definition blocks unrelated objects managed by the same definition

Team19d ago

#3579

Surface (or warn about) values a model method returns besides dataHandles, with sensitive-field support

Team19d ago

#3540

Cloudflare extensions reject account-owned API tokens: credential check uses /user/tokens/verify

Teams20d ago

#3046

serve: run scheduled workflows concurrently (per-workflow serialization), and report queue delay

Teams28d ago

#3080

serve --remote-only: step output from workers is never persisted to the run log (history logs always empty)

Teamz29d ago

#2468

serve: workflow trigger get/set ignore --config and read/write <repo>/.swamp/serve.yaml, so they disagree with the scheduler

Team1mo ago

#2472

serve --hot-reload: a changed trigger override schedule is logged as applied but the built-in cron keeps firing

Teams1mo ago

#2518

serve: a suspended run with an expired gate from a previous serve instance cannot be cancelled by any path

Teamz1mo ago

#3005

dashboard: approved autoResume run shows Resume and needs-inputs hint while serve already resumed it (status running)

Teams1mo ago

#3006

vault read-secret: to a pipe or file, drops the last line of a multi-line value when that line is 1024+ chars with no trailing newline (exit 0)

Teams1mo ago

#3010

s3-datastore/serve: readResource without a version returns an older version; the latest marker is rewritten backwards

Team20d ago

#2504

dashboard: Schedules/Webhooks views are empty for non-admins -- the health stream needs admin on access:* and the 403 is swallowed

Teams1mo ago

#2627

access token mint --server: server demands --vault, no client version has that flag

Team1mo ago

#2519

dashboard System tab shows Port —, TLS disabled, Auth —, Scheduling disabled although serve.config reports them correctly

Teams1mo ago

#2473

serve: remote token mint impossible with multiple vaults -- server demands --vault, CLI has no --vault option

Team1mo ago

#2465

workflows: a nested workflow step should inherit the caller's placement when the child declares none

Team19d ago

#2383

serve: minting a token for an unsupported principal kind (e.g. agent:) succeeds, then every connection 500s in parsePrincipal

Teams1mo ago

#2377

dashboard: an approved run never resumes and the dashboard cannot resume it (workflow.resume is never called)

Teams1mo ago

#2347

serve dashboard: 2.6 MB uncompressed per page (no permessage-deflate, unpaginated workflow/run search); 15 s WS close stall; serve.config rejected

Teams1mo ago

#2337

s3-datastore: since the #2300 conditional-write change, every push to Ceph RGW 19.2.5 fails (_meta.json 'kept changing'); the run still exits 0

Teamz1mo ago

#2298

s3-datastore: a transient S3 read error during a heartbeat silently abandons the lock; a second host then runs the same model concurrently

Teamz1mo ago

#2345

worker secret allowlist rejects caller-chosen vault references resolved at run time (method args carrying {vaultName, secretKey})

Team1mo ago

#2344

serve: default placement for steps that declare none (so one workflow runs both locally and via workers)

Team19d ago

#2339

s3-datastore: per-datastore AWS profile, so a serve audit store can use different credentials from the main datastore

Team1mo ago

#2325

SWAMP_SERVER_TOKEN is ignored with --server unless SWAMP_SERVER_URL is also set to the same host (and SWAMP_SERVER_URL rejects wss://)

Teams1mo ago

#2300

s3-datastore: verify conditional-write support (If-None-Match / If-Match) at setup and in doctor; a backend that ignores them makes locking silently unsafe

Teamz1mo ago

#2299

s3-datastore: documented offline behaviour is unreachable — lock acquire fails closed before pull, while a mid-run outage exits 0 with the data stranded

Team1mo ago

#1786

vault.get() arguments are verbatim, so a per-target secret cannot be expressed in workflow YAML

Teams2mo ago

#1950

model type describe reports arguments: {} for models that define a full args schema

Teams2mo ago

#1949

verification-attestation reports 0 skipped and omits skipped steps, including skipped asserts

Team2mo ago

#1785

Cancellation/--timeout skips remaining steps including `completed`/`always` branches; --timeout waits for the in-flight subprocess

Teams2mo ago

#1784

Remote "write-bearing" classification is inferred from data-plane writes, not declared; external side effects can be re-executed on worker disconnect (docs say the opposite)

Teams2mo ago

#1781

`workflow resume --from` does nothing for forEach steps whose template name contains `${{ }}`

Teams2mo ago

#1780

Step-level dependsOn on a forEach step never evaluates true (except `always`)

Teams2mo ago

#1782

manual_approval suspends the run while parallel sibling jobs are mid-flight; in-flight steps are torn down and left `running`

Teams2mo ago

#1792

CLI writes runtime state (lastStalenessWarning) into tracked .swamp.yaml, dirtying a committed config file

Teams2mo ago

#1788

workflow validate does not resolve modelType on factory-pattern steps — a non-existent extension validates clean

Teams2mo ago

#1789

Only documented non-interactive auth puts the password in argv; the safe SWAMP_API_KEY path is undocumented

Teams2mo ago

#1791

extension install serializes files[] in readdir order, producing machine-dependent reorder diffs in upstream_extensions.json

Teams2mo ago

#1790

Workflow YAML rewritten in place: block-scalar description truncated, file left unparseable, and validate still reports PASSED

Teams2mo ago

#1783

Audit timeline is not populated by swamp CLI commands unless the AI-tool hook fires (manual says recording is automatic)

Team2mo ago

← Back to list

01Issue

BugClosedSwamp CLIPublicTeam

AssigneesNone

Relationships

#2473 serve: remote token mint impossible with multiple vaults -- server demands --vault, CLI has no --vault option

Opened by randybias · 9/24/2026

Problem

With more than one vault configured, a token cannot be minted through --server at all.

$ swamp access token mint probe --principal user:probe --duration 15m --server wss://... --json
Server reported access_token_mint_failed: Multiple vaults are configured (mircloud-colo, _token-secrets). Pass --vault <name> to choose one.
$ swamp access token mint probe ... --vault _token-secrets --server wss://...
Unknown option "--vault".

The server asks for --vault, and the CLI has no such option (20260923.231117.0; swamp help access token mint lists none). Separately, access_token_mint.ts rejects a vault together with --server (tokenVaultRejectedMessage(... {remote: true})).

Why it matters

A mint done in-process through --server is exactly what --grant-reload auto picks up live. Blocking it forces operators to mint from a separate CLI process on the server host (kubectl exec, for us). The running server never sees that mint, so every new operator or automation token costs a server restart. For a single-replica deployment that restart is an outage. We have done it several times in one day.

Ask

Accept --vault on access token mint over --server, and pass it in the access.token.mint payload. Or let serve config name the vault used for token secrets.
Make the error message name an option that exists.

02Bog Flow

Closed

9/24/2026, 2:14:12 PM

No activity in this phase yet.

03Sludge Pulse

skunk-ape commented 9/24/2026, 2:14:12 PM

Thanks @randybias for this report, and especially for spelling out the operational cost: a restart per token, which is an outage on a single replica. That shaped how we tested the fix.

This is the same defect as #2466, which is now fixed in swamp-club/swamp#2606 and released as 20260924.140802.0-sha.daa5bb2c. Closing this as a duplicate.

On your two asks:

Accept --vault over --server, or a serve setting for the token vault. We did not add either. The serve now always stores remote-minted token secrets in the _token-secrets control-plane vault, as a local mint does, so no remote caller has to pick a vault. Keeping the vault a server-side constant also means a remote client cannot redirect where token secrets are stored.
Make the error name an option that exists. Remote mint can no longer produce that error.

On restarts: a token minted with --server is live on the running serve at once, with no restart. The restarts came from minting in a separate process (kubectl exec). With a remote datastore, a running serve does not pull the out-of-process token definition, so that token failed until the next boot. Minting through --server avoids that.

Two things to know:

The mint output does not include the credential, and swamp access token reveal has no --server. Run reveal where the serve repo or its datastore is reachable. That is a read, so it needs no restart.
With more than one replica, a mint reaches only the replica that handled it. The other replicas still need a restart to see it. Your single-replica setup is fully covered.

The new token still needs a grant before it can do anything. --grant-reload auto or swamp access reload picks that up live, as before.