ID-JAG explained: how AI agents get cross-app access under enterprise control
How ID-JAG and Cross App Access let a company's identity provider approve AI agent access to other apps, with lab screenshots and the draft's current status.
Build a DPoP proof with a key that lives only in this page, or paste one to check. I verify the signature against the embedded key and compare method, URL, nonce and token hash.
Runs in your browser. Nothing you paste is sent anywhere. Don't paste production private keys.
The page makes no network request while you work. The only exceptions are the buttons that say Fetch, which call the address you type. Keep real private keys out of any web page, including this one.
Use a test account and throwaway keys. Do not paste production secrets, session cookies or real users' tokens.
To check a proof, paste a DPoP JWT (typ dpop+jwt), plus the HTTP method and URL it was built for. You can also paste an access token to check ath, and a nonce. The builder needs no pasted key: it creates one in the page.
I generate an ES256 key with Web Crypto and keep it in this page's memory only. Reloading the page drops it.
Check a proof
Samples are made with throwaway keys and example.test names. They mean nothing outside this page.
To check a proof, paste a DPoP JWT (typ dpop+jwt), plus the HTTP method and URL it was built for. You can also paste an access token to check ath, and a nonce. The builder needs no pasted key: it creates one in the page.
A JWT with typ dpop+jwt, the public key in the header, and claims for the HTTP method, the URL, the time and, for resource calls, a hash of the access token.
It is the SHA-256 thumbprint of the proof key. The authorization server binds the access token to it in the cnf claim, so a stolen token is useless without the key.
Enter the method and URL in Build a proof and press Build proof. The page generates a P-256 key in your browser, signs the proof and shows the jkt you would see in cnf.jkt.
The newest posts and labs on the same topic, picked automatically.
How ID-JAG and Cross App Access let a company's identity provider approve AI agent access to other apps, with lab screenshots and the draft's current status.
Lab in a test tenant: device-code sign-in, an agent API exchanging the token on-behalf-of with a certificate and no secret, and an unconsented scope failing.
A lab with the official MCP Python SDK and Keycloak: the 401 handshake, audience checks, an RFC 8693 exchange for the payments API, and a refused passthrough.