GitHub Actions to Azure with workload identity federation: which runs get a token, and why
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.
Paste a SAMLRequest, a SAMLResponse or a redirect URL to decode it, check the signature and decrypt the assertion. I wrote this to debug logins without handing assertions to a stranger.
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.
The SAMLResponse or SAMLRequest value from a form POST, the raw XML, or the whole redirect URL. To decrypt an assertion, also paste a test private key, never a production one.
Samples are made with throwaway keys and example.test names. They mean nothing outside this page.
The SAMLResponse or SAMLRequest value from a form POST, the raw XML, or the whole redirect URL. To decrypt an assertion, also paste a test private key, never a production one.
Paste the base64 value from the SAMLResponse form field, the raw XML or the whole redirect URL. Deflate is handled for you, and the page shows the issuer, conditions, attributes and signature status.
Yes. Paste the service provider private key and it decrypts the EncryptedAssertion in your browser. Use a test key, never a production one.
The newest posts and labs on the same topic, picked automatically.
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.
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.
My reading of the IETF 127 OAuth and WIMSE sessions: ID-JAG, the Workload Authorization Grant, transaction tokens and actors, with draft revisions.