ToolsHub for browser-based developer tools

Identity debugging is a pile of one-off pages: a JWT decoder here, a JWKS fetch there, a SAML dump in another tab. A ToolsHub page now collects Authdog's free browser-based developer tools in one place.

This is the longer note behind the July 19 changelog entry.

How it works

ToolsHub is a landing page that links to the available browser utilities. The hub is for inspect-and-verify work you do before or beside a production integration: JWTs, SAML, TLS, OAuth, JWKS, OIDC discovery, and related checks.

The same release fixed dashboard UI issues that showed up while wiring the new page. Those fixes are console-shell polish, not a change to how hosted authentication or APIs behave.

ToolsHub does not replace the console, the CLI, or the Account Portal. It is a public toolbox. You do not need an Authdog project to open the hub.

Set it up

Nothing to configure.

Open Tools.
Pick the utility that matches the artifact you have (a token, a JWKS URL, a SAML response, a webhook signature).
Use a development issuer and non-production tokens when you paste samples.

When you are done inspecting, go back to the console to change environment settings. The hub does not write Authdog configuration.

Trust boundaries

These tools run in the browser on pages you open. Treat anything you paste as visible to that origin and to your clipboard history. Do not paste production private keys, environment API secrets (adenv_…), or live session cookies into a public debugger.

A green check in a playground is not server authentication. Validate sessions on your backend against the environment's public key and userinfo, as described in Sessions and tokens.

Try it

Open ToolsHub and run one inspector against a development document. The original release note is in the changelog.