Defining custom authentication parameters for mobile apps

Enable user authentication, either for Pega Mobile Client, against an external OAuth 2.0 server, or for Pega Infinity Mobile Client, against an Open Id Connect (OIDC) server, by defining a number of custom properties.

Before you begin: See the Overriding Channels and interfaces form settings with custom parameters Pega Community article.

Obtain the assets.zip file:
- If you plan to use Pega-default branding assets, download the branding-assets.zip file from Branding assets templates for various Pega Mobile Client and Pega Infinity Mobile Client versions.
- If you modified branding assets to meet your company's requirements, use the assets.zip file that contains these assets.
For more information, see Preparing custom branding assets.
Download the custom.properties file.
In the custom.properties file, define custom parameter values:
- If you are configuring authentication for Pega Mobile Client, against an external OAuth 2.0 server, update the parameters according to the list in Custom parameters for OAuth 2.0 ROPC authentication for mobile apps.
- If you are configuring authentication for Pega Infinity Mobile Client, against an external OIDC server, update the parameters according to the list in Custom parameters for direct authentication against an external OIDC server.
Place the custom.properties file in the root directory of the assets.zip file.
Upload the assets.zip file to Pega Platform.
For more information, see Uploading branding assets and custom modules.

What to do next:

If you are configuring authentication for Pega Mobile Client, against an external OAuth 2.0 server, return to Configuring user authentication with OAuth 2.0 tokens and ROPC flow for Pega Mobile Client-based mobile apps.
If you are configuring authentication for Pega Infinity Mobile Client, against an external OIDC server, return to Configuring direct authentication against an external OIDC server for Pega Infinity Mobile Client.