ops(secrets): Infisical Token Auth token forgejo-codex-runner expires 2026-08-12 — rotate before then #274

Open
opened 2026-05-14 09:21:06 +02:00 by codex · 3 comments
Collaborator

Context

Infisical Token Auth token for the Forgejo deploy runner was issued on 2026-05-14 after the Token Auth recovery work.

Token tracking

  • Token name: secret
  • Recommendation for next rotation: rename to forgejo-codex-runner-2026-05-14 or similar for clarity
  • Issued: 2026-05-14
  • Expires: 2026-08-12 (90-day TTL)
  • Action by: 2026-08-08 (4-day pre-expiry buffer)
  • Secret object id verified by operator: e5a9b50b-7b89-4d72-af78-0a0179cc0863

Rotation procedure

Use docs/ci/runner-contract.md section Lessons learned — Infisical Token Auth recovery (2026-05-13/14) after PR #273/#docs lands.

Expected high-level flow:

  1. Issue a new Infisical Token Auth token for the git.pdurlej.com runner machine identity.
  2. Keep TTL at least 30 days; 90 days recommended for persistent runner tokens.
  3. Persist new token locally and install on RS2000 via the runner-local Token Auth install procedure.
  4. Verify the runner can resolve p+codex@durlej.me via Infisical without printing values.
  5. Run a no-op smoke proving forgejo_token_source=infisical-token-auth.
  6. Revoke the old token only after the new one is proven.

References

  • #265 — Infisical Token Auth migration
  • #272 — direct PAT precedence blocker
  • #273 — resolver fix PR
  • #142 — RS2000 cutover lane

Closes when token is rotated before 2026-08-12.

## Context Infisical Token Auth token for the Forgejo deploy runner was issued on 2026-05-14 after the Token Auth recovery work. ## Token tracking - Token name: `secret` - Recommendation for next rotation: rename to `forgejo-codex-runner-2026-05-14` or similar for clarity - Issued: 2026-05-14 - Expires: 2026-08-12 (90-day TTL) - Action by: 2026-08-08 (4-day pre-expiry buffer) - Secret object id verified by operator: `e5a9b50b-7b89-4d72-af78-0a0179cc0863` ## Rotation procedure Use `docs/ci/runner-contract.md` section `Lessons learned — Infisical Token Auth recovery (2026-05-13/14)` after PR #273/#docs lands. Expected high-level flow: 1. Issue a new Infisical Token Auth token for the `git.pdurlej.com runner` machine identity. 2. Keep TTL at least 30 days; 90 days recommended for persistent runner tokens. 3. Persist new token locally and install on RS2000 via the runner-local Token Auth install procedure. 4. Verify the runner can resolve `p+codex@durlej.me` via Infisical without printing values. 5. Run a no-op smoke proving `forgejo_token_source=infisical-token-auth`. 6. Revoke the old token only after the new one is proven. ## References - #265 — Infisical Token Auth migration - #272 — direct PAT precedence blocker - #273 — resolver fix PR - #142 — RS2000 cutover lane Closes when token is rotated before 2026-08-12.
Author
Collaborator

M03 triage result: keep this open, but move it out of current M03 closeout.

Reason: this is a real scheduled Token Auth rotation tracker with action window before 2026-08-12. It is not evidence that the current secrets/access hardening lane is blocked tonight. No token values were read or printed.

Disposition: moved to M10 Improvements / scheduled maintenance backlog; keep owner-attention and class/security-sensitive because the eventual rotation is operator-sensitive.

M03 triage result: keep this open, but move it out of current M03 closeout. Reason: this is a real scheduled Token Auth rotation tracker with action window before 2026-08-12. It is not evidence that the current secrets/access hardening lane is blocked tonight. No token values were read or printed. Disposition: moved to M10 Improvements / scheduled maintenance backlog; keep `owner-attention` and `class/security-sensitive` because the eventual rotation is operator-sensitive.
Collaborator

Rotation runbook (M10 closure; p1, deadline 2026-08-12). Execution is operator/ops-gated (touches a secret); this is the ready runbook. Exact paths per state/reports/w4a-deploy-runner-token-auth-2026-05-24.md + runbooks/secrets-pipeline.md.

  1. Generate a new Infisical machine-identity client secret for the forgejo-codex-runner identity.
  2. Back up the runtime token file (.bak-<ts>), then update it atomically.
  3. Restart only forgejo-deploy-runner.service.
  4. Smoke: a platformctl-auto-apply.yml run → status success; confirm marker forgejo_token_source=infisical-token-auth.
  5. Revoke the old secret in Infisical; verify direct-fallback markers stay 0.
    Keep owner-attention. Disposition: runbook ready, execution scheduled before the deadline.
**Rotation runbook (M10 closure; p1, deadline 2026-08-12).** Execution is operator/ops-gated (touches a secret); this is the ready runbook. Exact paths per `state/reports/w4a-deploy-runner-token-auth-2026-05-24.md` + `runbooks/secrets-pipeline.md`. 1. Generate a new Infisical machine-identity client secret for the `forgejo-codex-runner` identity. 2. Back up the runtime token file (`.bak-<ts>`), then update it atomically. 3. Restart only `forgejo-deploy-runner.service`. 4. Smoke: a `platformctl-auto-apply.yml` run → status success; confirm marker `forgejo_token_source=infisical-token-auth`. 5. Revoke the old secret in Infisical; verify direct-fallback markers stay 0. Keep `owner-attention`. Disposition: runbook ready, execution scheduled before the deadline.
Collaborator

{
"confidence": 5,
"effort_hint": "medium",
"escalation": {
"kind": "operator",
"reason": "Runner token rotation involves security-sensitive credentials and owner-attention timing."
},
"evidence_refs": [
{
"note": "Issue tracks rotation of an Infisical Token Auth token for the Forgejo deploy runner before expiry.",
"type": "forgejo",
"value": "issue-title-body-labels-and-target-snapshot"
},
{
"note": "Body gives a dated rotation window, high-level procedure, and verification expectations for runner secret resolution.",
"type": "forgejo",
"value": "issue-body-rotation-procedure"
},
{
"note": "Snapshot labels mark the target as security-sensitive, owner-attention, and priority p1.",
"type": "snapshot",
"value": "target-snapshot-labels"
}
],
"impact": 5,
"judge_actor": {
"name": "iskra",
"runtime": "openclaw"
},
"judged_at": "2026-06-10T01:00:00Z",
"labels_to_apply": [
"judge/p1",
"judge/operator-needed"
],
"piotr_fit": "high",
"priority": "p1",
"rationale_summary": "This is P1 operator-needed security ops because runner credential rotation has a fixed expiry window and production access implications.",
"reach": 4,
"recommended_next_action": "operator_needed",
"rerun_reason": "no_prior_judgment",
"schema": "openclaw.judge.v0",
"target": {
"kind": "issue",
"number": 274,
"repo": "pdurlej/platform"
},
"target_snapshot": {
"body_hash": "sha256:452585b4b41cb5abf0b28a08c41208ef233f4b83fa5a7876e18dee2a4fd14fec",
"commit_count": null,
"evidence_hash": "sha256:69781d998ea62c81be27b9ba399f2b77e37c1cc56480b802766aa0e134d1c2b4",
"head_sha": null,
"labels": [
"class/security-sensitive",
"owner-attention",
"priority:p1"
],
"labels_hash": "sha256:a729fa7cb5844abad84c130dad5ff2ba8ac512ecdc841c53739573abec0b9f3a",
"state": "open",
"title_hash": "sha256:6d86e5ad83f39a899f882652ff93745001d0c9f94280213e5cbcfc7c2c4c48ee",
"updated_at": "2026-06-01T08:54:33+02:00"
},
"top_caveat": "Do not expose token material; perform rotation with verified rollback and post-rotation runner resolution checks."
}

<!-- openclaw.judge.v0 --> { "confidence": 5, "effort_hint": "medium", "escalation": { "kind": "operator", "reason": "Runner token rotation involves security-sensitive credentials and owner-attention timing." }, "evidence_refs": [ { "note": "Issue tracks rotation of an Infisical Token Auth token for the Forgejo deploy runner before expiry.", "type": "forgejo", "value": "issue-title-body-labels-and-target-snapshot" }, { "note": "Body gives a dated rotation window, high-level procedure, and verification expectations for runner secret resolution.", "type": "forgejo", "value": "issue-body-rotation-procedure" }, { "note": "Snapshot labels mark the target as security-sensitive, owner-attention, and priority p1.", "type": "snapshot", "value": "target-snapshot-labels" } ], "impact": 5, "judge_actor": { "name": "iskra", "runtime": "openclaw" }, "judged_at": "2026-06-10T01:00:00Z", "labels_to_apply": [ "judge/p1", "judge/operator-needed" ], "piotr_fit": "high", "priority": "p1", "rationale_summary": "This is P1 operator-needed security ops because runner credential rotation has a fixed expiry window and production access implications.", "reach": 4, "recommended_next_action": "operator_needed", "rerun_reason": "no_prior_judgment", "schema": "openclaw.judge.v0", "target": { "kind": "issue", "number": 274, "repo": "pdurlej/platform" }, "target_snapshot": { "body_hash": "sha256:452585b4b41cb5abf0b28a08c41208ef233f4b83fa5a7876e18dee2a4fd14fec", "commit_count": null, "evidence_hash": "sha256:69781d998ea62c81be27b9ba399f2b77e37c1cc56480b802766aa0e134d1c2b4", "head_sha": null, "labels": [ "class/security-sensitive", "owner-attention", "priority:p1" ], "labels_hash": "sha256:a729fa7cb5844abad84c130dad5ff2ba8ac512ecdc841c53739573abec0b9f3a", "state": "open", "title_hash": "sha256:6d86e5ad83f39a899f882652ff93745001d0c9f94280213e5cbcfc7c2c4c48ee", "updated_at": "2026-06-01T08:54:33+02:00" }, "top_caveat": "Do not expose token material; perform rotation with verified rollback and post-rotation runner resolution checks." } <!-- /openclaw.judge.v0 -->
Sign in to join this conversation.
No labels
W6d-automerge-calibration
agent/claude-code
agent/codex
agent/hermes
agent/iskra
agent/ollama
agent/patchwarden
automerge-candidate
class/security-sensitive
cutover-gate
dependency/blocked
dependency/blocks-others
dependency/cross-repo
dependency/needs-confirmation
domain:agents
domain:ci
domain:docs
domain:forgejo
domain:infra
domain:memory
domain:runtime
domain:signal
domain:ux
flow/architecture
flow/blocked
flow/deployed
flow/done
flow/implementation
flow/intake
flow/maintained
flow/observed
flow/ready
flow/refining
flow/retired
flow/review
iterating
judge/codex-candidate
judge/hermes-candidate
judge/low-confidence
judge/needs-refinement
judge/operator-needed
judge/p0
judge/p1
judge/p2
judge/p3
judge/park
judge/patchwarden-candidate
judge/stale-priority
kind/adr
kind/bug
kind/chore
kind/feature
kind/infra
kind/ops
kind/refactor
kind/research
large-impact
merge/auto
merge/manual
merge/manual-dependency-conflict
merge/manual-failing-tests
merge/manual-merge-conflict
merge/manual-missing-review
merge/manual-operator-preference
merge/manual-red-zone
merge/manual-security-sensitive
merge/manual-unclear-scope
merge/manual-unknown
meta
mode:operator-only
mode:patchwarden-iskra-approved
mode:safe-auto
needs-operator-decision
needs-triage
not-ready
observed/erroring
observed/needs-followup
observed/pending
observed/retire-candidate
observed/unused
observed/used
operator-emotional
owner-attention
phase/02
phase/03
priority:p0
priority:p1
priority:p2
priority:p3
proposed
ready-for-agent
ready-for-operator
recovery
review:claude-reviewed
review:codex-reviewed
review:dziadek-reviewed
review:needs-human
risk/exposure
risk/process
risk/product
risk/runtime
safety:external-write
safety:no-prod-mutation
safety:prod-impact
safety:secret-touch
size/large
size/medium
size/small
size/tiny
size/unknown
source/adr
source/agent-generated
source/manual
source/operator-chat
source/voice-note
status:blocked
status:codex-ready
status:merged:pending-evidence
status:needs-evidence
status:operator-needed
status:parked
tier/full
tier/lite
tier/stacked
tier:0-platform-substrate
tier:1-iskra-value-layer
tier:2-tools-products-modules
type:bug
type:chore
type:docs
type:feat
type:policy
type:research
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pdurlej/platform#274
No description provided.