# Fetch OIDC discovery and JWKS online

> Free OIDC discovery viewer. Read an issuer's .well-known document and JWKS in your browser, with warnings for missing PKCE, weak keys and risky grant types.

- URL: https://iamops.dev/tools/oidc-discovery/
- Markdown: https://iamops.dev/tools/oidc-discovery.md
- Language: en
- Runs in your browser, nothing is uploaded.

Fetch or paste a discovery document and its keys. I read these before I trust a new issuer.

## What can I paste here

An issuer URL, or the discovery JSON itself and the JWKS if the fetch is blocked by CORS.

## What it does

- Type an issuer and the page fetches its discovery document, or paste the JSON yourself.
- It lists the endpoints, supported algorithms and grants, and warns about missing S256 PKCE, plain PKCE, implicit flow and none algorithms.
- The JWKS view shows kid, key type, size, thumbprint and certificate expiry, and flags weak or duplicate keys.

## Example use

Enter the issuer of a test tenant, fetch the document, and see whether S256 PKCE and the authorization code grant are advertised.

## How to read the result

- The issuer in the document must equal the issuer you typed. A mismatch is a real problem: tokens will not validate.
- code_challenge_methods_supported should list S256. If the field is missing, the server may still support PKCE but does not say so.
- The thumbprint is the RFC 7638 JWK thumbprint, handy to compare keys across systems.
- Authorization servers that support ID-JAG advertise it in identity_chaining_requested_token_types_supported.

## What it does not do

- Fetching works only if the server allows cross-origin reads. Many do not. Then open the URL in a tab and paste the JSON.
- It does not validate the document against the full OIDC schema.
- It does not test the endpoints. It only reads what the server claims.

## Questions people ask

### What can I paste here

An issuer URL, or the discovery JSON itself and the JWKS if the fetch is blocked by CORS.

### Where is the OIDC discovery document?

At the issuer URL plus /.well-known/openid-configuration. OAuth servers may publish /.well-known/oauth-authorization-server instead. Type the issuer and the page fetches it.

### Why does the fetch fail for some issuers?

The browser needs CORS headers on the issuer. If they are missing, fetch the JSON with curl and paste it into the page.

## Related

- [Certificate decoder](https://iamops.dev/tools/certificate-decoder.md): Decode an X.509 certificate, chain or CSR and read SANs, expiry, key size, fingerprints and chain order. Paste PEM, base64 DER or hex. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/certificate-decoder/)
- [SAML decoder and verifier](https://iamops.dev/tools/saml.md): Decode a SAMLRequest or SAMLResponse, check the XML signature and decrypt an EncryptedAssertion. Paste base64, raw XML or a redirect URL. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/saml/)
- [JWT decoder and verifier](https://iamops.dev/tools/jwt.md): Decode a JSON Web Token, show claims and expiry as dates, and verify the signature. Paste a compact JWT, then an HMAC secret, PEM key, JWK or JWKS. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/jwt/)
- [ID-JAG inspector](https://iamops.dev/tools/id-jag.md): Inspect an Identity Assertion JWT Authorization Grant against the IETF draft and get the curl requests. Paste a compact ID-JAG token. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/id-jag/)
- [DPoP proof builder and checker](https://iamops.dev/tools/dpop.md): Build a DPoP proof with a fresh ES256 key, or check typ, htm, htu, iat, ath, nonce and the cnf.jkt thumbprint. Paste a DPoP JWT and the method and URL. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/dpop/)
- [PKCE generator](https://iamops.dev/tools/pkce.md): Generate a PKCE code verifier and S256 challenge, or check that a pair matches, with authorize and token snippets. Paste a verifier and optional challenge, or generate them here. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/pkce/)
- [Encoder and decoder](https://iamops.dev/tools/encoder-decoder.md): Encode or decode Base64, URL, hex, HTML entities, Unicode, gzip, deflate and the SAML redirect chain, with auto-detect. Paste the text. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/encoder-decoder/)
- [HAR inspector](https://iamops.dev/tools/har-inspector.md): Inspect a HAR file: filter requests, follow the OAuth or SAML flow, decode JWTs, and copy as curl with secrets redacted. Drop a HAR export from DevTools. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/har-inspector/)
- [HTTP client](https://iamops.dev/tools/http-client.md): Call an API from your browser with Basic, Bearer, an API key, or OAuth 2.0 (client credentials, authorization code with PKCE, device code, refresh, token exchange) and optional DPoP. Enter the URL and auth details, or paste a curl command, HAR or OpenAPI definition. The request goes from your browser, not through this site. If CORS blocks the call, the page offers curl instead. (https://iamops.dev/tools/http-client/)
- [SD-JWT and VC decoder](https://iamops.dev/tools/sd-jwt.md): Decode an SD-JWT or SD-JWT VC: split disclosures, recompute digests against _sd, and check the Key Binding JWT. Paste the compact string with ~ separators, and optionally the issuer JWK. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/sd-jwt/)
- [Passkey and WebAuthn decoder](https://iamops.dev/tools/webauthn.md): Decode a WebAuthn or passkey response: attestationObject, clientDataJSON and authenticator data, including flags, AAGUID, sign count and the COSE public key. Paste the credential JSON or the individual fields. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/webauthn/)
- [MCP auth discovery checker](https://iamops.dev/tools/mcp-auth.md): Check MCP authorization discovery: Protected Resource Metadata (RFC 9728) and the authorization server metadata, and flag missing PKCE S256, CIMD/DCR or resource indicators. Enter the server URL, or paste the JSON if CORS blocks the fetch. Requests go from your browser, nothing is uploaded to this site. (https://iamops.dev/tools/mcp-auth/)
- [Shared Signals SET decoder](https://iamops.dev/tools/shared-signals.md): Decode a Shared Signals Security Event Token (CAEP or RISC), explain the event type and the sub_id formats, and optionally verify the signature. Paste the SET JWT and optionally the transmitter JWKS. Runs in your browser, nothing is uploaded. (https://iamops.dev/tools/shared-signals/)
