C=USEnterprise compatibility →

Standards Interoperability Integration

Empirical findings, architectural synthesis, and test results from integrating the Kantara Initiative’s “UMA for Agents” (U4A) federated authorization profile with the CEQUS national identity and authority framework.

Core Architectural Invariant

Federated autonomous systems cannot unilaterally expand authority granted by human principals. When a purchasing agent interacts with an external vendor, the effective permission is the non-delegable intersection of three independent boundary sets:

effective_permission = supplier_UMA_permission ∩ buyer_CEQUS_delegation ∩ service_constraints

Neither the supplier’s authorization server (AS) nor the buyer’s principal authority can bypass the other. If the supplier AS issues an RPT, but the buyer’s delegation grant is revoked or the catalog price exceeds the buyer’s per-transaction limit, the transaction fails closed under the SQLite write lock before any tool effect commits.

1. Scope and Kantara U4A Profile Baseline

The Kantara Initiative’s User-Managed Access (UMA 2.0) work group, led by Eve Maler and Nick Gamb, published the candidate profile “UMA for Agents” (U4A) to govern federated machine-to-machine authorization across autonomous boundaries. In November 2026, the CEQUS engineering team implemented and evaluated the complete U4A profile against the CEQUS authority architecture across 15 test suites comprising 106 baseline tests and 31 advanced extension tests.

All external transactions in this integration are strictly synthetic: bounded to ≤ USD 100 within a synthetic maple syrup procurement catalog. Zero live funds, external credit facilities, or production directories are mutated.

2. UMA/U4A Federated Interoperability Architecture

The diagram below illustrates the end-to-end federated control path between the buyer domain (governed by C=US / CEQUS authority) and the supplier domain (governed by the Kantara U4A vendor AS and Resource Server):

UMA for Agents (U4A) and CEQUS Federated Authorization Architecture Architectural diagram showing the dual-domain federated model: Buyer Autonomous Domain on the left with human principal, primary agent, sub-agent, and CEQUS delegation engine; Supplier Autonomous Domain on the right with Authorization Server and Resource Server; and the non-delegable invariant triple intersection gate. BUYER DOMAIN (c=US / CEQUS Authority) Accountable Person (Resource Owner) Passkey / WebAuthn Hardware Attestation (YubiKey) · FIDO2 Policy Ceiling: Max $100 · Single-Agent Delegation · Maple Catalog Buyer Agent A (Client qc) RFC 8705 mTLS X.509 Cert CN=Agent-Maple-Buyer-01 IEEE 7012 Negotiation Client Submits PoP & Countersign Sub-Agent B (Client vt) RFC 8693 Token Exchange Lineage: act claim = Agent A Scope-Narrowed: order:view Cascading Revocation Target CEQUS Client-Side Clamping Envelope • CAEP SSE In-Memory Revocation Filter (O(1) Instant Invalidation) • Cumulative Budget Ledger & Velocity Limiter (≤ $100 Ceiling) • Human Kill-Switch / Active Directory Suspension Check • SQLite ACID Write-Lock Gate (Zero Stale-State Commits) Local Enforcement: Cannot Be Overridden by Supplier AS NON-DELEGABLE INVARIANT GATE effective_perm = supplier_UMA ∩ buyer_CEQUS ∩ service_rules • If Supplier AS issues RPT but CEQUS revoked: FAIL CLOSED (403) • If CEQUS valid but Supplier Ticket unapproved: FAIL CLOSED (401) • If Price / Currency mismatch catalog: FAIL CLOSED (400) DETERMINISTIC ATOMIC COMMIT OR TOTAL ROLLBACK SUPPLIER DOMAIN (Kantara U4A Vendor) Supplier Authorization Server (U4A / Node AS) AS Perimeter Defense: TLS cert == initial cnf (No Token Theft) • IEEE 7012 Bilateral Contract Engine: need_info + Proffered Terms • Async Approval Queue: request_submitted (HTTP 403) & /owner/decide • RPT Issuer: Issues RFC 8705 cnf-bound Requesting Party Token • RFC 8693 Sub-Delegation Validator (Scope narrowing enforcement) • OpenID CAEP Broadcaster: /backchannel/sse (RFC 8935 SETs) Lightweight Node AS (Cold Start < 280ms vs 25s Keycloak) Supplier Resource Server (RS: e.g. /api/purchase) • Protection API Token (PAT) & UMA Ticket Minting (POST /tickets) • Unauthenticated Challenge: HTTP 401 + as_uri + ticket • Dual PoP Verifier: RFC 8705 (mTLS) & RFC 9421 (HTTP Signatures) • RFC 7662 Token Introspection Client (with PAT) • Persistent CAEP SSE Listener: Updates local in-memory filter • Order Fulfillment: Synthetic Maple Catalog (≤ $100 Ceiling) Protected Resource: POST /purchase Verified against both RPT claims and local buyer delegation state 1. 401 + Ticket 2. Ticket Exch & Terms 3. RPT + PoP (mTLS) 4. Introspect 5. CAEP SET
Figure 1: Federated UMA for Agents (U4A) and CEQUS Authority Architecture. The buyer domain (left) enforces local budget caps, passkey-authorized delegation, and in-memory CAEP revocation. The supplier domain (right) enforces AS perimeter defense, IEEE 7012 bilateral contract negotiation, supervisor async queues, and dual proof-of-possession. The transaction commits only when the non-delegable triple intersection is satisfied under the local SQLite write lock.

3. Key Findings Across the Integration Dimensions

Dimension 1: Authorization Server Architecture & Perimeter Defense

The initial capability gate was evaluated against a stock enterprise Keycloak 26.8.2 server deployed in a WSL2 Docker container. The investigation surfaced critical architectural trade-offs:

Dimension 2: Proof-of-Possession (PoP) Dual Support

CEQUS Resource Servers enforce strict proof-of-possession across two complementary IETF standards:

Dimension 3: IEEE 7012 Machine-Readable Bilateral Contracts

Kantara U4A anticipates machine-readable terms negotiation prior to granting access. Rather than relying on simple URL acknowledgment strings, we engineered a full bilateral contract engine (security/uma/terms.mjs):

Dimension 4: RFC 8693 Multi-Hop Agent Sub-Delegation

Complex enterprise purchasing requires primary procurement agents to delegate tasks to specialized sub-agents (e.g. logistics or inventory verifiers). We implemented RFC 8693 OAuth 2.0 Token Exchange for agent hierarchies (security/uma/token-exchange.mjs):

Dimension 5: OpenID CAEP / SSE Backchannel Push-Revocation

Under conventional OAuth/UMA architectures, Resource Servers rely on cached token introspection or short TTLs (e.g. 1,000 ms), leaving a window of vulnerability between administrative revocation and local enforcement. We implemented OpenID Continuous Access Evaluation Profile (CAEP) push-revocation (security/uma/caep-receiver.mjs):

Dimension 6: Live Owner Approval Queue & Supervisor Dashboard

When an agent requests operations exceeding automated policy thresholds (e.g. high-value orders or novel vendors), the ticket enters an asynchronous human approval state:

4. Architectural Refinements Discovered During Empirical Testing

Deploying and verifying the complete UMA/U4A test matrix surfaced five key architectural discoveries that required modifying baseline assumptions:

4.1 AS Perimeter Defense (Eliminating Lazy Introspection)

Conventional UMA architectures assume the Authorization Server is identity-agnostic during ticket exchange, leaving token verification to the downstream Resource Server’s introspection call. When evaluated against stock Keycloak 26.8.2, an attacker agent (Agent B) presenting an initial token stolen from Agent A at /ticket/exchange received an RPT bound to Agent B’s certificate. Our lightweight Node AS eliminates this vulnerability by enforcing mutual TLS verification directly at the AS perimeter: the caller’s TLS certificate SHA-256 thumbprint must match the cnf["x5t#S256"] claim in the incoming subject_token, failing closed with HTTP 400 invalid_grant before ticket evaluation occurs.

4.2 Zero-Latency CAEP Push Revocation (Eliminating the 1,000ms Exposure Window)

Early drafts relied on short token TTLs (1,000 ms) or periodic introspection polling. In multi-worker race condition tests (revocation-ordering.test.mjs and caep-revocation.test.mjs), a concurrent process could commit a purchase during the 1,000 ms window after an administrative kill switch signal was triggered. The architecture was revised to use OpenID Continuous Access Evaluation Profile (CAEP) Security Event Tokens (RFC 8935 SETs) pushed over persistent Server-Sent Events (/backchannel/sse). The Resource Server and the CEQUS delegation core maintain an in-memory hash set filter that invalidates tokens in O(1) time under the SQLite transaction write lock, reducing revocation latency from 1,000 ms to sub-millisecond local enforcement.

4.3 Interactive Bilateral Contract State Machine (IEEE 7012 need_info)

Traditional OAuth architectures treat Terms of Service as unilateral click-wrap links. Autonomous AI agents cannot legally or deterministically consent to unconstrained vendor terms. In our implementation (security/uma/terms.mjs), the UMA HTTP 403 need_info challenge was formalized into an interactive bilateral contract negotiation: the supplier AS proffers machine-readable clauses (data retention ceilings, dispute jurisdiction, synthetic liability caps, and mandatory Merkle logging); the buyer agent evaluates the proffer against its principal’s delegation policy and submits a cryptographically signed bilateral countersignature before the AS mints the RPT.

4.4 Bounded Exponential Backoff for Human-in-the-Loop Supervision

When an agent requests permissions exceeding autonomous policy thresholds (e.g., first-time suppliers or order values approaching the $100 ceiling), synchronous HTTP connection holds cause worker starvation and gateway timeouts. We refined the protocol into an asynchronous supervisor queue: the AS returns HTTP 403 request_submitted and dispatches a webhook to the resource owner. The buyer agent enters a bounded exponential backoff polling loop (1s → 2s → 4s, maximum 5 attempts). When the human supervisor approves or denies the ticket via the live dashboard (POST /owner/decide), the agent’s subsequent poll immediately resolves or fails closed with grant_denied_by_owner.

4.5 Strict 1:1 Identity Mapping Invariant

Multi-tenant agent gateways frequently suffer from confused deputy attacks if certificate-to-client mappings permit many-to-one or one-to-many associations. In security/uma/fixtures.mjs and security/delegation/core.mjs, the mapping schema was tightened to enforce strict 1:1 bidirectional uniqueness: exactly one client ID per X.509 certificate thumbprint and exactly one certificate per client ID. Any unmapped client or lookalike certificate is rejected immediately with resource_authorization_identity_mismatch.

5. Standards Interoperability Matrix

Standard / SpecificationGoverning BodyArchitecture RoleStatusImplementation & Evidence
UMA 2.0 (Grant & Federated Authz) Kantara Initiative Federated ticket-to-token exchange across autonomous domains TESTED Tested on local Keycloak 26.8.2 and Node reference AS; 15 suites (112 tests) in security/uma/tests/TEST-PLAN.md. Closes token-theft gap via receiver-side certificate binding checks.
UMA for Agents (U4A Candidate) Kantara Initiative Agent-specific identity binding, async approvals, terms negotiation UNIT-TESTED Project reference implementation in security/uma/local/node-as/; dual PoP, IEEE 7012 contract engine, async queue, and Merkle evidence witness in testbed. Draft profile; not an enterprise product.
RFC 8705 (mTLS Token Binding) IETF OAuth WG Certificate-bound access tokens via cnf["x5t#S256"] TESTED Validated against Keycloak 26 and native Node AS; verified across DER/PEM representations.
RFC 9421 (HTTP Message Signatures) IETF HTTPbis WG Per-request cryptographic request signatures over message headers TESTED security/uma/http-sig.mjs; Ed25519 signatures over Signature, Signature-Input, Signature-Agent.
IEEE 7012 (Machine-Readable Terms) IEEE P7012 WG Machine-negotiable bilateral procurement contracts TESTED security/uma/terms.mjs; automated proffer, negotiation, and bilateral countersigning verified in ieee-7012-engine.test.mjs.
RFC 8693 (OAuth 2.0 Token Exchange) IETF OAuth WG Multi-hop agent sub-delegation with scope narrowing and act claim TESTED security/uma/token-exchange.mjs; hierarchical agent token exchange verified in subdelegation.test.mjs.
OpenID CAEP / SSE (RFC 8935 SETs) OpenID Foundation Backchannel push-revocation over mTLS Server-Sent Events TESTED security/uma/caep-receiver.mjs; zero-latency fail-closed revocation verified in caep-revocation.test.mjs.
RFC 7662 (Token Introspection) IETF OAuth WG Token active status and certificate binding verification TESTED Native Node AS returns active: true and cnf; verified in node-as.test.mjs.
W3C WebAuthn / FIDO2 W3C / FIDO Alliance Hardware-attested human supervisor approval and kill switch TESTED YubiKey hardware attestation, PIN-protected enrollment, Windows Hello passkey stop drills.
X.500 / LDAPv3 (RFC 4511) ITU-T / IETF Hierarchical registry under c=US and c=CA TESTED OpenLDAP (slapd 2.6) live directory; chained cross-border queries between c=US and c=CA.

6. Empirical Verification & Test Matrix

All automated test suites pass with a 100% success rate on clean development environments and GitHub Actions CI:

Suite CommandScope / FocusTestsPassedSkippedDuration
npm run test:uma:node-asNode AS, IEEE 7012, RFC 8693, CAEP, Owner Queue424203.3s
npm run test:uma:plan15-Suite Baseline Kantara U4A Test Plan112112051.2s
npm run test:umaUMA Core Contract & Purchase Service313103.7s
npm run test:vda:remoteRemote Execution & Fault Invariants60582 (POSIX)8.3s
npm run test:residuePackage Mirror & Filesystem Isolation7709.4s
npm run test:complianceNIST / CMMC Requirement Traceability111101.6s
npm run test:delegationFull CEQUS Delegation Engine594588639.8s

7. Limits and Academic Classification

Sources & Technical References