Step 5: Send the authorize request

GET {{authPath}}/{{envID}}/as/authorize?response_type=code&client_id={{SPAppWithAuthCodeGrantID}}&redirect_uri=https://example.com&scope=openid&code_challenge={{code_challenge}}&code_challenge_method=S256

The PingOne authorization endpoint /{{envID}}/as/authorize is used to interact with the resource owner and obtain an authorization grant. The authorization request must include values for the following properties:

• client_id

A string that specifies the application's UUID, which was returned in Step 1.

• response_type

A string that specifies the code or token type returned by an authorization request. For this activity, the value is token.

• redirect_uri

A string that specifies the URL that specifies the return entry point of the application. The redirect_uri property value defined in Step 1 is https://example.com.

• scope

A string that specifies permissions that determine the resources that the application can access.

• code_challenge

A value computed from the code_verifier property that is used in a PKCE authorization request.

• code_challenge_method

The computation logic used to generate the code_challenge string. The token endpoint uses this method to verify the code_verifier for PKCE authorization requests. Options are: plain and S256.

Note: If you use the Qodex collection, this request includes a pre-request script that creates the PKCE code_verifier and code_challenge strings and writes these values to your Qodex environment. If you do not use the Qodex collection, you can use the PingOne PKCE Code Generator application to obtain these strings.

The response returns a 302 message with a flowID embedded in the Location header, which specifies that a call should be made to another resource to continue the authentication flow. The Location header looks like this:

Location: https://apps.pingone.com/5caa81af-ec05-41ff-a709-c7378007a99c/signon/?flowId=03e52d0a-c55a-4807-889b-cd14f74ec4c5

Note: If this call fails to return a 302 HTTP Status, for a possible solution see Configuring and managing Qodex.

When the flow finishes, it returns an access token.

Request Params

HEADERS