Skip to main content
LinkedIn
Copied!

Table of Contents

Configuring direct authentication against an external OIDC server for Pega Infinity Mobile Client

Version:

Only available versions of this content are shown in the dropdown

Increase the security of your application by configuring Pega Infinity Mobile Client to authenticate mobile users directly against an external OpenID Connect (OIDC) identity provider through the OIDC authorization code authentication flow.

In this scenario, users authenticate once against an external identity provider that complies with the OIDC standard. Subsequent access to Pega Platform requires a token that comes from the OAuth 2.0 authorization layer.
If you configure Pega Mobile Client to authenticate directly against an external OIDC identity provider, Pega Platform ignores any settings that you configure on the mobile channel configuration page, in the Select authentication service field.
Pega Platform does not automatically create IDs for operators when they attempt to log in. Create all potential operator IDs in advance. For more information, see Creating an operator ID.
Prepare for the configuration of the direct user authentication against an external OIDC server by learning about accessing Pega Platform from external applications. For more information, see Authenticating requests in services.
  1. Configure the client registration service.

  2. Enable the mobile authentication service.

  3. Prepare and upload the app.properties file.

You can generate the mobile app executable files. For more information, see Generating installation packages.
Suggest Edit
Did you find this content helpful?

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us