Initiate an authorization request
GET/oauth2/auth
Initiates the authorization flow by redirecting the resource owner's user-agent through
the authorization server. Supports Authorization Code (response_type=code), Implicit
(response_type=token or id_token), and Hybrid flows as defined in
RFC 6749 and
OpenID Connect Core 1.0.
PKCE (RFC 7636) and Pushed Authorization
Requests (RFC 9126) via request_uri are
also supported.
On success the user-agent is redirected to redirect_uri with the authorization code or
tokens appended as query parameters (code flow) or in the fragment (implicit/hybrid flows).
On error the user-agent is redirected to redirect_uri with error and
error_description query parameters, unless redirect_uri itself is missing or invalid.
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