Answers to common questions — and the fastest ways to get unstuck.
Get help
The step-by-step guide covers installing, every view, sharing captures and all the settings.
Found a bug or have a feature idea? Open an issue on GitHub — it's the best place to track it.
Awesome SAML Tracer is free. If it saves you time, a coffee on Ko-fi keeps it going.
FAQ
Yes. The extension is free to install and use from the Chrome Web Store. If it saves you time, you can optionally support development on Ko-fi — but that's entirely up to you.
No. Everything the extension captures stays on your device. It uses Chrome's local storage APIs and never transmits data to any server — including the developer's. There's no analytics and no third-party services. See the privacy policy for the full detail.
Awesome SAML Tracer is a modern, Manifest V3 rebuild. On top of decoding SAML messages, it adds a friendly-name attribute table, a built-in JWT decoder, self-contained HTML reports, an errors-only view, domain highlighting and pinned headers. It reads and writes the same JSON export format, so captures move freely between the two tools.
A few things to check:
Yes. Awesome SAML Tracer imports and exports the same JSON format as the original SAML-tracer. Use the 📂 Import button or drag-and-drop a .json file anywhere onto the window. Files exported from Awesome SAML Tracer also open in the original extension.
Chrome 111 or newer. It also runs on Chromium-based browsers that support Manifest V3 extensions and the Chrome Web Store, such as recent versions of Edge and Brave.
The extension requests only what it needs to observe SAML traffic locally:
webRequest — to observe network requests and detect SAML messagesstorage — to save captures and settings locally on your devicetabs — to open the extension window and manage its badgedownloads — to save HTML reports to your Downloads folder<all_urls> — SAML SSO can occur on any domain, so it must observe requests to any URLFull detail is in the privacy policy.
You have three options:
Up to 200 captures at a time. When that limit is reached, the oldest entries are dropped automatically. You can clear everything at any time with the ⊘ Clear button.
Open an issue on the GitHub issue tracker. Including your Chrome version and, where possible, an exported JSON capture or HTML report makes bugs much faster to reproduce and fix.
If the FAQ didn't cover it, open an issue on GitHub and describe what you're seeing — it's the best way to get a fix or an answer.