Skip to content

Add reusable owner-approved preview agent access - #63

Merged
intel352 merged 7 commits into
mainfrom
feat/managed-agent-access-20261009
Oct 11, 2026
Merged

intel352 merged 7 commits into
mainfrom
feat/managed-agent-access-20261009

Conversation

@intel352

@intel352 intel352 commented Oct 9, 2026 •

Copy link
Copy Markdown
Contributor

Preview assistants currently have no narrowly authorized application identity. This adds opt-in native agentidentity grants with owner approval/revocation, registered public-key RFC7523 exchange, and current tenant/resource authorization. Declarative policies support multiple preview sites with separate grants, page-body CAS ceilings and protected-view audiences; adding a preview requires configuration and owner approval.

The authoritative PostgreSQL adapter persists grants/public keys, globally unique assertion identities, token revocations and retained transactional audit. Owner management uses the same adapter as token validation. Storage/audit failures deny access. Human sessions, factors and bootstrap rows remain separate. The exchange accepts no human-cookie, client-secret, refresh or legacy-HMAC fallback.

Validation at 169e5e6e2920a60728f3d8e83980ec52006b49fc: CI37968416999 passed the full race suite, vet and contracts. All seven real PostgreSQL 17 integration tests passed with no database skips, covering two-tenant service exchange/authorization, current owner filtering, 24-way global replay, reconnect, expiry/revocation, SQL constraints and transactional audit rollback. All PR checks passed. Local focused race/vet passed 107 cases (24 top-level); no local database or Docker ran. Exact native owner HTML passed 11 local browser checks including confirmation, second-tenant selection, reload/revoke, 375px keyboard layout and measured text contrast. The browser fixture is synthetic and provides no hosted activation proof.

Independent whole-source review approved the exact final head; all four findings were resolved. Final review receipt SHA256: d59874db709fe6a61a0df9ad4c31548bede2646f12ef529d02a82daf7a5a12e1. The invalid database-fixture API routes caught during review are corrected, with an always-running constructor check before any absent-database skip. Production route validation remains strict.

Adoption is separate: explicit SQL is unapplied; no key, credential, persistent grant, host mount, release, schema change or deployment is performed by this PR. A matched released Workflow IssueManagedToken API (Workflow#1043), approved protected key custody, current human owner policy, CAS-aware CMS integration and separately reviewed protected-view gate are required. The current Basic review host does not accept agent tokens yet.

This draft includes the reviewed design documentation from #62, preserving that frozen branch. Shared mechanisms contain no Tina tenant/page literals; the two-site example is policy only and creates no access. CMS/schema/host adoption and actual owner-factor/hosted browser verification remain blocked until their separate prerequisites are satisfied.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant