Token Binding

Token Binding establishes a cryptographic binding between an application-layer bearer token and the TLS connection over which it is presented. During the TLS handshake, the client proves possession of a private key, and the resulting Token Binding ID is included in a Token-Binding HTTP header. The server then validates that the token is bound to that specific TLS channel. If an attacker exports the token and attempts to replay it from a different connection, the binding mismatch causes immediate rejection. This effectively neutralizes token export attacks and replay attacks that plague traditional bearer token architectures.

The protocol supports two binding modes:

• Provided Token Binding: The client generates a new key pair and presents the Token Binding ID directly to the server in the same TLS connection. This is the standard mode for direct client-server communication.
• Referred Token Binding: Used in federation scenarios where a token is obtained from one endpoint but presented to another. The client proves possession of the same key pair across both connections, allowing the resource server to cryptographically verify that the presenter is the same entity that obtained the token. This is critical for OAuth 2.0 and OpenID Connect flows in multi-agent mesh networks.

The Token Binding ID is a structured identifier that uniquely identifies a binding between a client's key pair and a TLS connection. It consists of:

• Binding Type: Specifies the cryptographic algorithm, such as Token Binding over HTTP.
• Key Parameters: The public key of the client's Token Binding key pair, typically an Elliptic Curve (EC) key.
• Signature: A cryptographic proof that the client possesses the corresponding private key, signed over the Exported Keying Material (EKM) from the TLS handshake. This ensures the binding is non-exportable and non-transferable across different TLS sessions.

In federated identity architectures, Referred Token Binding enables secure token chaining across security domains. When an agent obtains an access token from an Identity Provider (IdP), it presents a Provided Token Binding. When presenting that token to a Resource Server, the agent includes a Referred Token Binding that references the original Token Binding ID and proves possession of the same private key. The Resource Server can verify the entire chain, ensuring the token was not intercepted and replayed by a malicious intermediary. This is essential for Zero Trust agent mesh networks where no implicit trust exists between nodes.

Token Binding incorporates privacy protections to prevent cross-session tracking. Clients can generate a new Token Binding key pair for each TLS connection or origin, preventing servers from correlating user activity across sessions. The protocol also supports Token Binding key rotation, where keys are periodically refreshed to limit the exposure window if a key is compromised. This aligns with privacy-by-design principles and prevents the Token Binding ID itself from becoming a persistent tracking vector in agent communication networks.

Token Binding extends OAuth 2.0 and OpenID Connect by adding a cnf (confirmation) claim to access tokens and ID tokens. This claim contains the SHA-256 hash of the Token Binding ID, cryptographically binding the token to the client's key pair. When the token is presented, the resource server validates that the Token Binding ID in the HTTP header matches the hash embedded in the token. This prevents token replay even if the token is intercepted via man-in-the-middle attacks or malware on the client device. The binding is transparent to application logic and enforced at the protocol layer.

A property of secure communication protocols where the compromise of a long-term private key does not compromise past session keys. Each session derives ephemeral keys that are discarded after use.

• Achieved through ephemeral Diffie-Hellman key exchange
• Critical for agent communication logs that may be stored long-term
• Ensures historical intercepted traffic remains encrypted even after a breach