This activity shows you how to create a sign-on policy with a progressive profiling action, initiate an authorization request, and use the flow APIs to complete the progressive profiling action.

The following operations are supported by the PingOne APIs:

Workflow order of operations

To complete a progressive profiling flow, the following tasks must be completed successfully:

  1. Make a POST request to /environments/{environmentId}/applications to add a new application to the specified environment.

  2. Make a GET request to /environments/{environmentId}/applications/{applicationId}/secret to return the new application’s secret attribute.

  3. Make a GET request to /environments/{environmentId}/resources to return a list of all resource entities associated with the specified environment to get the ID for the PingOne platform resource.

  4. Make a GET request to /environments/{environmentId}/resources/{resourceId}/scopes to list all scopes associated with a specified resource (the PingOne platform resource).

  5. Make a POST request to /environments/{environmentId}/applications/{applicationId}/grants to create a new resource access grant for the application.

  6. Make a POST request to /environments/{environmentId}/signOnPolicies to create a new sign-on policy that referneces the flow definition resource.

  7. Make a POST request to /environments/{environmentId}/signOnPolicies/{signOnPolicyId}/actions to define the login action associated with this sign-on policy.

  8. Make a POST request to /environments/{environmentId}/signOnPolicies/{signOnPolicyId}/actions to define the progressive profiling action associated with this sign-on policy.

  9. Make a POST request to /environments/{environmentId}/applications/{applicationId}/signOnPolicyAssignments to associate the sign-on policy with the application.

  10. Make a POST request to /environments/{id}/populations to create a new population resource.

  11. Make a POST request to /environments/{id}/users to create a user who will be assigned to the new population resource.

  12. Make a POST request to /environments/{id}/users/{userId}/password to set the new user’s password.

  13. Make a POST request to /{environmentId}/as/authorize to obtain an authorization grant. This request starts the authorization flow.

  14. Make a GET request to /{environmentId}/flows/{flowID} to initiate the flow.

  15. To complete the login action, make a POST request to GET /{environmentId}/flows/{flowID} and provide the user’s login credentials.

  16. To complete the progressive profiling action, make a POST request to GET /{environmentId}/flows/{flowID} and provide the user’s mobile phone number.

  17. Make a GET request to /{environmentId}/as/resume?flowId={flowID} to call the resume endpoint and return the auth code.

  18. After the authorization flow completes, make a POST request to /{environmentId}/as/token to exchange the auth code for an access token.

  19. Make a GET request to /environments/{environmentId}/users/{userId} to view the updated information about the identified user.

Click the Run in Postman button below to download the Postman collection for this use case.

Run in Postman