Configuring external authentication for a mobile app

Configuring external authentication for a mobile app

Description	Configuring authentication for a mobile app by using different protocols and external identity providers.
Version as of	8.2
Application	Pega Platform
Capability/Industry Area	Mobile

Authentication with external providers

In real-life deployments, access to Pega-based applications often needs to be secured with authentication against an external identity provider, such as Okta or Auth0. In particular, this requirement affects mobile apps that are based on Pega Mobile Client™.

Pega Platform™ provides out-of-the-box capabilities to configure such authentication by using OpenID Connect (OIDC) or Security Assertion Markup Language 2.0 (SAML 2.0) protocols. Below is a collection of links to tutorials that describe configuration and troubleshooting of external authentication with different identity providers.

Configuring authentication with OIDC

• Configuring OIDC authentication with Okta
• Configuring OIDC authentication with Auth0
• Configuring OIDC authentication with miniOrange
• Troubleshooting OIDC integrations

Configuring authentication with SAML

• Configuring SAML authentication with Auth0
• Configuring SAML authentication with miniOrange

A business solution that automates workflows in your organization. Multiple, unrelated applications can be hosted in the same system. You create an application by running the New Application wizard.

Tools to develop apps that work on a wide range of mobile devices. By building native apps that users can install on their Android and iOS devices, you can use mobile capabilities and improve the user experience. For example, Pega Mobile users can access their content at all times, which helps them be productive regardless of network connection status.

The process or action of verifying the identity of a user or system. Authentication in Pega Platform ensures that only users and systems with verified identities can access resources such as web pages, APIs, and data.

Used to generate legacy document types. A requirement is an event, condition, or function that must be satisfied and tracked by an application. Requirements can be functional (a capability) or non-functional (a quality or constraint). One or more requirements can be used to define the criteria for the successful implementation of a specification.

An ordered sequence of rules to run. In each step of a collection, you can define a precondition that is evaluated before execution, and a response action that runs after the step is completed.