Submit an authorization request
POST/oauth2/auth
Alternative to the GET form that accepts authorization request parameters as a
URL-encoded form body instead of query parameters. Support for POST is optional
per RFC 6749 Section 3.1; servers are required to support GET.
Note: Pushed Authorization Requests (PAR) use a separate dedicated PAR endpoint
for the initial POST — the subsequent call to this authorization endpoint then
carries only client_id and request_uri via GET.
Response codes and redirect behaviour are the same as for the GET endpoint.
Refer to the introduction section for details on how to configure this use case.
Request
Responses
- 302
- 400
Authorization result delivered via redirect to redirect_uri
Invalid request — returned when redirect_uri is missing or does not match any registered URI and the error cannot be communicated via redirect