How to use OAuth and OIDC Client Configuration Audit
- Choose Use the declarations below for the form, or advanced JSON for the documented public subset. In advanced mode, a selected UTF-8 JSON file replaces the JSON text.
- Select browser, native or confidential web client and supply endpoint URLs, redirect URIs, response/grant types and the declared client-authentication method. Enter no credentials.
- Declare the PKCE, state, exact-redirect and optional OIDC/nonce settings to review. These checkboxes describe intended behavior; they do not test it.
- Run Review client settings. Read each declared check and its scope, then download the JSON worksheet if needed. Compare findings with the actual application and provider configuration separately.
Example: OAuth and OIDC Client Configuration Audit
Review the supplied browser-client authorization-code configuration with S256 and declared state/nonce binding.
Options
- Configuration input
- Review local declarations only. No provider is contacted and no secret or token is accepted.
- Client type
- Choose Browser application (SPA), Native application, Confidential web application.
- Authorization endpoint
- The initial value is https://login.example/authorize.
- Token endpoint
- The initial value is https://login.example/token.
- Declared OIDC issuer
- Reviewed as a URL only when OIDC is selected. Discovery, ownership and trust remain unverified.
- Registered redirect URIs
- One absolute URI per line, at most 50. Exact registration and app control are not tested.
- Declared response types
- Comma-separated values. The supported scenario uses code; other declarations receive a review finding.
- Declared grant types
- Comma-separated values. Authorization code and optional refresh_token are the supported scenario.
- PKCE method
- Choose S256, plain, none.
- Token endpoint client authentication
- Declare the method only. Never enter its secret or private key.
- State binding is required by configuration
- Declares that this client requires state binding. The report reviews that declaration; it does not test the application or provider.
- This client uses OIDC
- Includes the declared issuer and nonce requirements in the OIDC review. Discovery and issuer trust remain unverified.
- OIDC nonce binding is required by configuration
- Declares nonce binding for the OIDC scenario. Selecting it does not prove that returned ID tokens are checked.
- Exact redirect matching is required by configuration
- Declares that registered redirect URIs must match exactly. The tool cannot verify the provider registration or runtime matching.
- Advanced public configuration JSON
- Used only in advanced JSON mode. The documented public subset is accepted; secrets, tokens and unknown properties are refused.
- Advanced public configuration file (optional)
- One UTF-8 JSON file up to 256 KiB. In advanced mode, the selected file takes priority over the JSON text.
Supported inputs and limits
- A supported local declaration subset, not an OAuth/OIDC implementation or compliance check.
- Advanced input accepts the documented public properties only; secret, token and unknown properties are refused.
- A selected UTF-8 JSON file is limited to 256 KiB.
- Endpoints and OIDC issuer are checked as supported URL forms, while redirect registration, app ownership, issuer discovery and runtime bindings remain unverified.
- No provider call or configuration change is made.
Where your input is processed
This tool does not upload your inputs. See the limits for anything saved on your device.
Configuration is one part of the flow
A registered redirect and a PKCE setting must still be enforced by the actual provider and client. This review cannot discover that behavior. Use the findings to compare the declared configuration with the intended client type; do not treat a clear report as protocol or security certification.
Questions about OAuth and OIDC Client Configuration Audit
Should I include a client secret?
No. This review uses public configuration and refuses secret fields.
Does it test my provider?
No. It compares the supplied declarations with its supported offline rules.
Will it change a redirect?
No. Findings are a worksheet for deliberate review in the real application.