OAUTH 2.0 · EXPERIMENTAL COMMUNITY DEMO

From authorization to API.

Choose a flow. Get a token. See what it can access.

Demo serverauth.quarkus-authorization-server.dev ↗

01 / CONFIGURE

Authorization Code + PKCE

Sign in and consent on the authorization server, then exchange the returned code. User login and client authentication are separate steps; the demo client secret is prefilled.

Public demo credentials are prefilled. Edited values and tokens stay in memory; redirect state and PKCE use temporary session storage. Reset restores the demo defaults.

02 / TOKEN

Your token will appear here

Complete a flow to inspect its claims and call the resource server.

Authorize→Token→API

03 / RESOURCE SERVERBearer

Put the scopes to work.

Each API requires its matching scope. Missing token → 401. Missing scope → 403.

REQUEST LOG0 / 20

Requests appear as you interact. Credentials and tokens are redacted from this log.