Step 4: Send an authorization request

GET {{authPath}}/{{envID}}/as/authorize?response_type=code&client_id={{dvFlowAppID}}&redirect_uri=http://localhost:3000/login/callback&scope=openid

This example shows the GET /{{envID}}/as/authorize operation to send an authorization request to the PingOne authorization server.

Note: For authorization and flow requests, the PingOne endpoint domain is https://auth.pingone.com/ for North America.

In this request:

• {{envID}} represents your environment ID.

• response_type here has a value of code. In other cases, it can be token, id_token, or a combination of these.

• client_id is the ID of the PingOne application that you created in a prior step.

• redirect_uri identifies the redirect URI that you specified when you created the PingOne application.

• scope specifies the OpenID Connect (OIDC) user claims are included in the token.

• The request returns a 200 message when successful. The response body contains HTML that creates the sign-on form.

See the following topics to learn more:

• OpenID Connect/OAuth 2

• Authorization

• Authorize (authorization_code)

• API Toolkit: Authorization and Authentication APIs

Request Params