Configuring user authentication with OAuth 2.0 tokens and ROPC flow for Pega Mobile Client-based mobile apps

You can configure Pega Platform to support user authentication against an external OAuth 2.0 server, using the Resource Owner Password Credentials (ROPC) authentication flow. In this scenario, a Pega Mobile Client-based mobile app does not send user credentials to the Pega Platform. Instead, the app sends user credentials to the OAuth 2.0 server for validation. The OAuth 2.0 server returns the access token that is then used to connect to Pega Platform.

Before you begin: Make sure that you have a working instance of the OAuth 2.0 authorization server that is configured to use the ROPC grant type.

To configure user authentication with OAuth 2.0 tokens you must perform the following tasks:

  1. Defining custom authentication parameters for mobile apps.
  2. Creating dynamic system settings for OAuth 2.0 ROPC authentication for mobile apps.
  3. Creating a custom authentication service for OAuth 2.0 ROPC authentication for mobile apps.
  4. Creating a keystore for OAuth 2.0 ROPC authentication for mobile apps.
  5. Configuring a service package for OAuth 2.0 ROPC authentication for mobile apps.
  6. Creating operator ID instances for OAuth 2.0 ROPC authentication for mobile apps.
  7. Setting up an alternative host.
  8. Generating installation packages.