Control Plane by Karl McGuinness

Enterprise SaaS Needs OAuth Federation Now

public@karlmcguinness.com (Karl McGuinness) — Sun, 19 Apr 2026 20:05:00 -0700

Enterprise SaaS still defaults to app-by-app OAuth islands with their own clients, long-lived artifacts, and revocation paths. The architectural shift is OAuth federation: adopt issuer-mediated federation now for services and workloads, and adopt Cross-App Access (XAA) as the standards direction for user-delegated cross-app access.

AAuth Now Has a Mission Layer

public@karlmcguinness.com (Karl McGuinness) — Mon, 13 Apr 2026 11:21:00 -0700

The new version of AAuth (draft-hardt-aauth-protocol-01) materially changes the earlier comparison. Mission is now first-class in the protocol, with PS-mediated approval, mission-aware token choreography, and governance endpoints. The remaining gap is no longer whether Mission exists, but whether the published model is strong enough to support portable containment rather than just mission correlation and governance hooks.

Implementing Mission Architecture End to End

public@karlmcguinness.com (Karl McGuinness) — Sat, 11 Apr 2026 10:30:00 -0700

The full implementation spec for Mission architecture: how to compile a bounded authority record from user intent, project it into Cedar policies and audience-specific OAuth tokens, enforce it at the host and MCP tool boundary, gate irreversible actions at the commit boundary, and keep the governance model operational through template ownership, revocation SLAs, audit integrity tiers, and an operator console built around decisions not raw artifacts. Includes V1 product contract, sequenced build plan, configuration management, and a complete test appendix.

ID-JAG Beyond the Enterprise IdP

public@karlmcguinness.com (Karl McGuinness) — Sun, 05 Apr 2026 12:00:00 -0700

ID-JAG, also often called Cross-App Access (XAA), is centered in the current draft on Enterprise IdP trust, but the issuer that matters is the immediate IdP the downstream authorization server already trusts for SSO and subject resolution, not necessarily the top-level workforce IdP. The same trust pattern can also extend architecturally to CIAM and platform identity layers that federate upstream workforce login while remaining authoritative for downstream product trust, tenant context, and subject resolution.

AgentPass and the Missing Mission Layer

public@karlmcguinness.com (Karl McGuinness) — Tue, 24 Mar 2026 09:00:00 -0700

AgentPass introduces an Authority as a separate governance entity that approves and scopes agent access before credentials are issued. The architecture converges with Mission-Bound OAuth in important ways. But the Task description problem, the scope compilation gap, and the thin lifecycle model are precisely where the Mission and Mission Shaping work picks up.

Where Mission Lives in the IAM Stack

public@karlmcguinness.com (Karl McGuinness) — Mon, 23 Mar 2026 09:00:00 -0700

Mission has to live somewhere as a durable authority record. This post places Mission in the IAM stack as a system of record for delegated authority, distinct from tokens, PDP decisions, the commit boundary, and orchestrator state.

Open-World OAuth Still Needs Mission Shaping

public@karlmcguinness.com (Karl McGuinness) — Sat, 21 Mar 2026 10:00:00 -0700

Open-world OAuth can improve discovery, resource binding, and first-contact trust. That still leaves the harder agent problem: how approved intent becomes bounded authority that stays governed across delegation chains, unfamiliar tools, consent expansion, revocation, and task termination.

OAuth for Open-World Ecosystems

public@karlmcguinness.com (Karl McGuinness) — Fri, 20 Mar 2026 10:00:00 -0700

OAuth was built for closed worlds, and that constraint is why it became mature. Agents expose the limits of that deployment model. This post traces what the newer OAuth standards get right and which substrate gaps still need to close.

Standardize `act` Across Assertion Grants and JWT Access Tokens

public@karlmcguinness.com (Karl McGuinness) — Wed, 18 Mar 2026 10:30:00 -0700

The current split between token exchange semantics and JWT access token practice creates avoidable interoperability failures. A common profile for act, grounded in entity profiles, can align JWT assertion grant and JWT access token processing.

Mission Shaping Is Not Enough

public@karlmcguinness.com (Karl McGuinness) — Wed, 18 Mar 2026 09:00:00 -0700

Part 2 turns from the semantic problem to the runtime one. Quiet expansion, delegation, headless execution, stale state, and open-world execution all push Mission shaping past its strongest domain. Containment and runtime governance carry more of the safety burden.

The Mission Shaping Problem

public@karlmcguinness.com (Karl McGuinness) — Tue, 17 Mar 2026 09:00:00 -0700

This essay picks up from Part 4 of the Mission-Bound OAuth series and focuses on the first hard problem: how approved intent becomes a governable Mission. In structured domains that can look like staged Mission shaping or compilation. Many current deployments still do not do it at all.

Why Mission-Bound OAuth Might Be the Wrong Answer

public@karlmcguinness.com (Karl McGuinness) — Sun, 15 Mar 2026 12:00:00 -0700

Mission-Bound OAuth is a serious attempt to govern delegated agent authority using existing OAuth infrastructure. This post takes the pessimistic view: it may be the wrong answer because it asks the authorization server to become a governance engine, a lifecycle controller, and a mission ledger all at once. A cleaner alternative is to treat Mission as a separate authority service and let OAuth be one projection of that model rather than its home.

Mission Architecture on AAuth

public@karlmcguinness.com (Karl McGuinness) — Sun, 15 Mar 2026 09:00:00 -0700

Mission-Bound OAuth argues for a durable Mission object that governs delegated authority across approval, lifecycle, delegation, and termination. This follow-up asks whether Dick Hardt’s AAuth draft is a better protocol substrate for the same model, and where AAuth still appears to need an explicit Mission-like authority object.

Client Context and ID-JAG for Mission-Bound OAuth

public@karlmcguinness.com (Karl McGuinness) — Sat, 14 Mar 2026 09:00:00 -0700

Rich Authorization Requests are the natural first instinct for agent missions, but audience-bound access tokens and uneven cross-domain interoperability limit how far they can carry a governed task. Mission-Bound OAuth solves that by making the Mission a durable authority object at the authorization server. This post explores the authentication-layer companion profile: OpenID Connect Client Context carries purpose and approval input when the user is present, and ID-JAG carries reduced Mission projections across same-IdP trust domains.

Mission-Bound OAuth

public@karlmcguinness.com (Karl McGuinness) — Fri, 13 Mar 2026 09:00:00 -0700

OAuth answers whether a request is permitted right now. Mission-Bound OAuth asks whether a delegated mission should still be running at all. This RFC proposes a durable Mission object at the Authorization Server that governs token derivation, lifecycle, delegation, and termination across agent execution.

Agents Don't Need Your Passport. They Need Your Authority.

public@karlmcguinness.com (Karl McGuinness) — Sat, 21 Feb 2026 22:59:09 -0800

Enterprise IAM was designed for human-paced execution. Agents remove the presence, pacing, and natural scope-limiting that made those controls work. The result is a structural gap that stronger credentials, tighter scopes, and faster JIT provisioning cannot close.

From Passports to Power of Attorney

public@karlmcguinness.com (Karl McGuinness) — Sat, 21 Feb 2026 22:59:09 -0800

Tokens, credentials, and scopes tell a system what an agent may do. They say nothing about why execution was authorized or when it should end. The Execution Mandate is the primitive that closes that gap: a signed, inspectable authority record that runtime systems can evaluate and revoke throughout the execution lifecycle.

Governing the Stay, Not Just the Entry

public@karlmcguinness.com (Karl McGuinness) — Sat, 21 Feb 2026 22:59:09 -0800

An Execution Mandate defines what delegated authority looks like. This post builds the control plane that makes it operational: how mandates are issued and held as authoritative artifacts, how authority is evaluated continuously rather than at gates, how governance crosses organizational boundaries, and where enforcement lands in practice.

About

public@karlmcguinness.com (Karl McGuinness) — Sat, 21 Feb 2026 00:00:00 +0000

I’m Karl McGuinness, a product and technology leader with 25+ years of experience building mission-critical, internet-scale identity and infrastructure platforms. At Okta, I spent over a decade helping modern enterprises and the broader industry treat identity as foundational infrastructure.

I specialize in product architecture, the intersection of product strategy and system design. I translate ambiguous requirements into durable product structures: domain boundaries, APIs, platform extensibility, and investment sequencing that keep teams fast today and options open later.

Welcome to Control Plane

public@karlmcguinness.com (Karl McGuinness) — Mon, 28 Apr 2025 23:22:40 -0700

Identity is getting weird again, and in a good way.

This blog is where I post hot takes, field notes, and analysis on identity, security, and agentic systems. Some posts will be tactical. Some will be opinionated. Some will be me zooming out and asking, “are we solving the right problem at all?”

Lately I keep coming back to one thing: most of our stack is great at deciding who can get in, and still pretty weak at governing what autonomous systems should keep doing over time.