Push an authorization request to Auth0 and receive a request URI to use in the authorization flow. PAR enhances security by moving authorization parameters from the front channel (browser) to the back channel (direct server-to-server).
Benefits:
How it works:
request_uri in response/authorize with only client_id and request_urirequest_uriThe access token received from the authorization server in the OAuth 2.0 flow.
Your application's Client ID
Must be 'code' for PAR
code Your application's Client Secret (required for confidential clients)
The redirect URI for your application
Space-delimited list of requested scopes
An opaque value to maintain state between request and callback
The unique identifier of the target API
The PKCE code challenge
The method used to generate the code challenge
S256 A random string value for ID Token validation
A JWT signed with your client secret or private key (for Private Key JWT authentication)
Must be 'urn:ietf:params:oauth:client-assertion-type:jwt-bearer' when using client_assertion
urn:ietf:params:oauth:client-assertion-type:jwt-bearer