Configuring user authentication with OAuth 2.0 tokens and ROPC flow for Pega Mobile Client-based custom 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 custom 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.

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. Define custom parameters.
  2. Create Dynamic System Settings.
  3. Create a custom authentication service.
  4. Create a keystore.
  5. Configure the service package.
  6. Create operator instances.
  7. Set an alternative server URL.
  8. Build a custom mobile app.