Beta

Create a tenant

A new tenant starts with its own users, OAuth settings, audit history and logs. You are its first Tenant Admin.

Authorization request builder

Build an OAuth 2.0 or OpenID Connect authorization request one parameter at a time, or paste an existing one to read it back.

Everything happens in this browser. What you paste is not sent or stored, and leaving the page clears it.

The builder only writes the URL. Opening it sends you to the provider, just as a client would.

Start from an existing request

Paste a full URL to load its parameters into the form below.

Request

Provider and client

From the provider's discovery document, for example https://login.example.test/authorize.

Must exactly match a redirect URI registered for the client.

What to ask for

code with PKCE is the recommended flow. Types that include token return tokens through the browser.

Space-separated. openid makes it an OpenID Connect request.

Protection

state ties the response to this browser, nonce ties an ID token to this request, and PKCE ties the code to the client that asked for it.

Optional parameters

prompt

An email address or identifier to fill in at the provider.

Seconds since the user last authenticated before they must sign in again.

Requested authentication context classes, space-separated.

Preferred languages, such as en-GB fr.

One absolute URI per line: the APIs the token is for (RFC 8707).

A JSON array for rich authorization requests (RFC 9396).

One name=value per line, for parameters the form does not cover.

Authorization request

We value your privacy

We use cookies and similar technologies to enhance your browsing experience, and analytics to understand our traffic. By clicking "Allow all", you consent to optional analytics. Cookie Policy

Tools