TIDP - Auth Server Demo [Codename: test me, if you can]
Step 01
βοΈ
Config
Step 02
π
PKCE
Step 03
π€
PAR
Step 04
π
Auth
Step 05
π
Token
Step 06
π€
UserInfo
Step 07
β»
Refresh
Step 08
πͺ
Logout
π Guide
Select a flow step to see more information.
β‘ Presets
Presets fill all endpoints & client config. Auto-discover uses Issuer
URL.
Environments & Tenants
Environments and Tenants influence the Issuer / Base URL and
Authorization endpoints.
Client Config
Authorization Server
PKCE Parameters RFC 7636
Generate a cryptographically random code_verifier and derive the code_challenge. These
values will be used throughout the flow.
Code Verifier (keep secret)
Code Challenge (send to server)
Challenge Method
Verifier Length
Pushed Authorization Request RFC 9126
POST the authorization parameters directly to the PAR endpoint. The server returns a request_uri that you use in place of all parameters in the redirect.
POST payload preview:
Request URI
Expires In
Authorization Redirect RFC 6749
Redirect the user-agent to the authorization endpoint. The URL contains only client_id and the request_uri from PAR (or full params if PAR was skipped).
Callback β Code Received incoming
Authorization Code
State (verified)
Issuer
Callback β Error
Error
Description
Token Exchange authorization_code
Exchange the authorization code for tokens. The code_verifier is sent to prove possession of
the PKCE secret.