Connection Hub

One authority for delegated access in an ecosystem of services, agents, and automations.

The identity provider exists because many applications need one authority on who the user is. Delegated access needs its own authority the same way: when agents, automations, and external tools act on a user's behalf against many services, someone has to hold the answer to "what may this caller do right now, for which user, on which accounts". Connection Hub is that component.

Every caller gets its own delegated-access card: a live, versioned record of whose authority it uses, which resources and operations it may reach, which connected accounts it may touch, and until when. The deployment publishes an active capability catalog: the ceiling of what may be delegated at all. A guarded service resolves the current card intersected with the active catalog on every call. Authorization never travels inside tokens, so there is nothing to copy between executions, and an edit or revocation applies on the very next call.

Each granted operation can also be always available or limited to one invocation. That usage policy is a separate live record, so consuming one use does not rewrite the user's card.

user (grantor) --edits/revokes--> +----------- Connection Hub -----------+
                                  | delegated cards: one per caller,     |
                                  | versioned, with a current pointer    |
                                  | active capability catalog: the       |
                                  | deployment ceiling, versioned        |
                                  +------------------+-------------------+
                                                     | resolved per call:
caller --opaque bearer--> guarded operation boundary | bearer x current card
                                                     | x active catalog
                                  allow with bounded authority, or a
                                  structured denial the caller can act on

This package is for both sides of that boundary:

• service owners who want their operations admitted through the hub: registration, per-call admission, workload proof, structured denials;
• client and agent authors whose code calls guarded services: the client SDK, grant checks, one-call tokens, denial-driven consent.

The package is the portable core: contracts, state machines, admission evaluation, OAuth protocol builders, the client SDK. A host supplies HTTP routes, sessions, storage, and secret resolution. KDCube is the first host (the complete Connection Hub application ships in this repository as connection-hub@1-0); a standalone service host is planned.

Install

python -m pip install connection-hub

A caller that signs in to a Connection Hub resource and keeps its credentials on its own machine (a desktop tool, a coding-agent host such as Problem Board's pb) installs the caller side:

python -m pip install "connection-hub[client]"

That adds connection_hub.caller: sign-in in a browser or by device code, profiles, credentials in the operating system's native store, and an authenticated MCP connection (build_caller_services, connect_profile_tools). It needs no KDCube package. The connection-hub command line is a thin shell over it.

Current release: 2026.09.28.0307, the first with the client extra.

The current release supports owner-configured OAuth for external MCP connectors. The browser flow uses MCP protected-resource and authorization-server discovery, PKCE, a Client ID Metadata Document, dynamic registration, or a provider-console client, server-side token storage, serialized refresh, and upstream revocation. The existing transport protocol remains compatible for direct-credential hosts.

Device proof, encrypted delivery, and durable authority

Hosts and clients use one product-owned wire implementation from connection_hub.delegated_credentials.devices. It generates exportable P-256 keys for native host custody, signs and verifies request-bound ES256 proofs, and encrypts bounded JSON packages with ECDH-ES/A256GCM:

from connection_hub.delegated_credentials.devices import (
    build_device_proof,
    decrypt_device_package,
    generate_device_key,
    verify_device_proof,
)

Proof verification binds the embedded public key, HTTP method, normalized target URI, server nonce, proof id, and a short issuance window. Package decryption requires the exact protected delivery bindings supplied by the caller. Algorithms are fixed by the API and malformed P-256 points are rejected before signature verification or decryption.

The same package owns the reusable authority behind those wire contracts. PostgresProfileDeviceAuthority records profile devices, their credential families, recovery attempts, and short-lived device-encrypted packages in one PostgreSQL transaction boundary. Package fetches return the same ciphertext until the device acknowledges delivery, record each fetch, and clear the ciphertext on every terminal transition. Token plaintext and delivery nonces are never stored in PostgreSQL. RedisDeviceProofState keeps only run-fenced, one-use nonce and replay state whose loss costs a retry.

The integrating host verifies each request proof before invoking a consuming authority transition, supplies the current immutable Card revision, and owns HTTP policy, PostgreSQL/Redis lifecycle, and native credential custody. The private key and decrypted token set remain in the client host's native credential store. Importing the authority does not activate a runtime or migrate an existing store; host composition and migration are explicit operations.

Flow 1: a guarded service registers itself and admits calls

A backend that wants the hub to regulate its admissions does three things.

Register once (configuration on the hub, not code): declare the capability rows the service exposes (grants, resources, operations) in the hub's delegated catalog, and register the service as a workload: a service id, a secret reference, and selectors of the declared resources. The registration does not restate operations; the catalog stays the single vocabulary both sides speak.

Per request, ask for admission. The caller arrives with an opaque delegated bearer. The service builds the semantic request, signs it with its own workload secret (possession of a user bearer is not service identity), and asks the hub:

import secrets, time

from connection_hub.delegated_credentials.admission import (
    AdmissionRequest,
    sign_admission_request,
)

request = AdmissionRequest(
    resource="https://api.example.test/customers",
    operation="customers.search",
)
timestamp = str(int(time.time()))
nonce = secrets.token_urlsafe(24)
signature = sign_admission_request(
    secret=service_signing_secret,
    service_id="crm-api",
    timestamp=timestamp,
    nonce=nonce,
    delegated_token=user_delegated_bearer,
    request=request,
)
# POST request.signing_dict() to the hub's admission endpoint with
# Authorization: Bearer <user_delegated_bearer> and the four
# X-Connection-Hub-* proof headers (service id, timestamp, nonce, signature).

Enforce the decision. An allow carries a pairwise service-scoped user id, a separate pairwise caller-profile id, and only the bounded authority for that one operation. It never carries provider credentials, raw card/client ids, or the platform's internal user id. A denial is structured and actionable:

{
  "ok": false, "allowed": false,
  "schema": "connection_hub.delegated_admission.v1",
  "error": {"code": "delegated_capability_not_granted",
             "message": "...", "retryable": false},
  "ret": {"reason": "delegated_capability_not_granted",
           "details": {"resource": "...", "claims": ["..."]}}
}

The service still applies its own domain rules after admission; the hub answers delegation, the service answers business.

For a once operation, the service supplies a stable invocation id and request digest. Connection Hub can replay its admission decision. A service that changes domain state also records the effect under that invocation id because the effect happens outside Connection Hub.

Runnable end to end: the direct-admission-service example and the deployment recipe.

Flow 2: an external client connects through OAuth

When an external agent client (Claude Code through its connector, or any MCP client) reaches a guarded service, the hub runs the handshake:

external client                       Connection Hub host
  | 1. call the service URL without a credential
  |    <- 401 + WWW-Authenticate, protected-resource metadata (RFC 9728)
  | 2. fetch authorization-server metadata (RFC 8414; also served as
  |    openid-configuration so strict clients proceed)
  | 3. identify: pre-registered client, client-id URL (CIMD), or
  |    dynamic registration (DCR)
  | 4. authorize with PKCE (S256 required)
  |    -> the USER logs in, consents per capability, and binds the
  |       exact connected accounts the client may use
  | 5. exchange the single-use code (60 s) for an opaque bearer (1 h,
  |    rotating refresh); a delegated card is created for this client
  | 6. every subsequent call resolves the current card and active
  |    catalog; nothing is decided from the token alone
  | 7. the user edits or revokes the card at any time; the very next
  |    call obeys (RFC 7009 revocation retires the card too)

The consent screen is not a blanket yes: the user selects capabilities and binds specific provider accounts, and that selection becomes the card. Full protocol, descriptor contract, and failure modes: OAuth delegated credential protocol.

Flow 3: proxying a user-owned external MCP service

A remote MCP server does not need a Connection Hub integration. Its owner adds the streamable-HTTP endpoint and optional upstream bearer/header credential to Connection Hub. The credential stays in the server-side owner secret store. Discovery creates an owner-scoped resource whose exact accepted tools can be selected on each caller card.

The delegated caller connects to the Connection Hub remote_mcp_proxy with its own opaque bearer. The proxy lists only that card's selected tools, compares the live tool descriptor with the accepted descriptor, applies once or always, injects the upstream credential, and calls the remote server. Because the proxy performs the call, a retry with the same invocation id and arguments can return the stored terminal result without redispatch.

Flow 4: calling from code, the client SDK

A hosted agent or application talks to the hub through ConnectionsClient over a one-method host transport:

from connection_hub import ConnectionsClient

client = ConnectionsClient(transport)  # transport: async call(operation, payload)

# what is connected, and what may this caller do
entries = await client.catalog()                       # list[CatalogEntry]
check = await client.agent_grant_check(
    client_id="kdcube-agent:myapp:myagent",
    namespace="mem", operation="object.search",
)                                                       # governed/granted + claims

# one-call credentials, resolved by the hub, never stored by the caller
token = await client.get_token("google", account_id="acc-1")
bearer = await client.agent_grant_token(
    client_id="kdcube-agent:myapp:myagent",
    resource="https://host/api/public/mcp/named_services",
)                                                       # None while consent is pending

When a call is denied because a consent is missing, the denial carries everything needed to recover: which permission, which provider, which account, and where the user grants it. The mcp_consent module turns such denials into a structured ask the agent can surface and retry after the grant lands.

What the package owns, and what a host supplies

The package owns portable authority semantics: versioned cards and catalogs, once-or-always invocation policy and idempotency records, external MCP connector/proxy contracts, per-call admission for managed REST, MCP, and named-service calls, the OAuth protocol builders, connected-account policy, structured denials, the client SDK, server-side login (connection_hub.server_side_login: one HttpOnly cookie, sliding renewal, an OIDC authenticator and a Google Identity Services authenticator), and explicit ports for storage, identity, dispatch, secrets, and live delivery. The host supplies the HTTP surfaces, authenticated sessions, durable storage and its Redis projections, secret resolution, and the UI. The boundary is documented in package extraction architecture.

For resident Card bearers, ResidentCardSecretService owns the portable cross-store lifecycle. The host supplies PostgreSQL-backed CardHandleMetadataStore and an expiring ResidentSecretStore. Secret records are created atomically under fresh opaque references; metadata stores only the reference and SHA-256 fingerprint. Before the host write, PostgreSQL records a prepared intent containing that reference, binding metadata, and expiry, never the bearer. The metadata installation transaction consumes the intent and returns the exact outgoing reference it recorded for cleanup. Rotation and retirement delete the verified secret before acknowledging its durable cleanup record, while reads compare the access id, Card revision, fingerprint, and expiry before returning the bearer. Host creation atomically refuses a live reference collision without overwriting it, and stale-reference resolution fails closed on the envelope binding. A lost create or metadata response leaves a durable address for reconciliation; cleanup verifies the envelope and first guards against deleting a current reference. Cleanup is claimed durably before host I/O, failed attempts retain their reason and exponential retry time, and a prepared intent selected for cleanup can no longer be installed. A host that binds both ports gets a custody boundary formed by PostgreSQL and its secret provider.

A refused host create quarantines its prepared intent through that same claim-and-retry protocol. It neither drops the custody address nor deletes the colliding host record; verified cleanup converges after the bounded foreign record expires.

Documentation

• Configuration and capabilities overview
• Connection Hub architecture and semantic requirements
• Delegated authority and admission
• Delegated access cards
• OAuth delegated credential protocol
• Server-side login
• Direct protected-service recipe
• Release procedure

License: MIT. Source: https://github.com/elenaviter/app-ecosystem