Enforce downscoping in token exchange for agent-to-agent calls
A Keycloak lab for A2A agents: the token B gets for C follows B's own scopes, not A's, unless you enforce downscoping. Stock run, control run and the fix.
Paste what navigator.credentials returned. I decode the CBOR, name the authenticator when I can and check the attestation and sign-in signatures.
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.
const cred = await navigator.credentials.create(options); // or .get()
console.log(JSON.stringify(cred.toJSON()));MDN: toJSON()Use a test account and throwaway keys. Do not paste production secrets, session cookies or real users' tokens.
A WebAuthn registration or authentication JSON (the credential from navigator.credentials), or the fields separately: clientDataJSON and attestationObject for a registration, or clientDataJSON, authenticatorData, signature and the public key for an assertion.
Registration (create)
Sign-in (get)
Authenticator names come from a bundled list built from Microsoft Entra documentation (MicrosoftDocs/entra-docs) (MIT), web.dev: Determine the passkey provider with AAGUID (CC BY 4.0).
Samples are made with throwaway keys and example.test names. They mean nothing outside this page.
A WebAuthn registration or authentication JSON (the credential from navigator.credentials), or the fields separately: clientDataJSON and attestationObject for a registration, or clientDataJSON, authenticatorData, signature and the public key for an assertion.
BE (backup eligible) says the credential can be synced to other devices. BS (backup state) says it is synced now. Both are set for most passkeys in Apple, Google and password manager apps.
Some providers send a zero AAGUID on purpose, usually with none attestation. The relying party then cannot tell the model, and this tool shows it as not disclosed.
The newest posts and labs on the same topic, picked automatically.
A Keycloak lab for A2A agents: the token B gets for C follows B's own scopes, not A's, unless you enforce downscoping. Stock run, control run and the fix.
Lab: a GitHub workflow signs in to Azure with no secret. I print the sub of six kinds of run and show which credential lets each one in, pull requests too.
My reading of the IETF 127 OAuth and WIMSE sessions: ID-JAG, the Workload Authorization Grant, transaction tokens and actors, with draft revisions.