Published Release Notes

All search data is encrypted

All search data in Pega Cloud deployments is now encrypted, both at rest and in transit. The encryption of search data makes search compliant with regulatory requirements.

For more information about search, see Full-text search.

Authentication service for basic credentials

A new type of authentication service is available for authenticating operators by using basic credentials (user ID and password). The default Pega Platform™ login is now an instance of this type of authentication service. All basic credentials authentication services include mobile authentication with the OAuth 2.0 protocol and Proof Key for Code Exchange (PKCE). You no longer have to create a custom authentication service to support mobile applications.

For more information, see Configuring a basic authentication service.

Unauthenticated sessions transition seamlessly to authenticated

A new authentication service type allows a guest user to use an application without logging in, and to be prompted to authenticate later in the session. This enhancement supports scenarios such as online shopping portals where a user can browse for items and load a shopping cart as a guest but be prompted for credentials at checkout.

For more information, see Configuring an anonymous authentication service.

Create single sign-on authentication services from App Studio

You can create and enable single sign-on (SSO) authentication services from a new landing page in App Studio. From this new landing page you can also configure new SAML and OpenID Connect authentication services to provision users. For more information, see Creating a SAML SSO authentication service and Creating an OIDC SSO authentication service.

Protect against insecure deserialization

Deserialization is the process of rebuilding a data stream into a Java object. The Open Web Application Security Project (OWASP) has identified insecure deserialization as one of the top 10 security vulnerabilities for web applications. Pega Platform™ protects against this vulnerability by using filters that prevent deserialization of suspect data streams. You can configure these filters from the Deserialization Blacklist landing page.

For more information, see Configuring the deserialization filter.

Support for Firebase Cloud Messaging (FCM) push notifications in Android custom mobile apps

You can now create Android custom mobile apps that use push notifications with the Firebase Cloud Messaging (FCM) services. The push notifications for Android custom mobile apps based on legacy Google Cloud Messaging (GCM) are deprecated, as GCM services will be officially removed from use on April 11, 2019. To continue to use push notifications, you must migrate your custom mobile apps to FCM services. Before building your custom mobile app, you must register your Android app for push notifications in the Firebase console, obtain the FCM server key and Google Services JSON file, and use the key and file in the Android certificate set to build the custom mobile app.

For more information, see Migrating Android custom mobile apps that use push notifications to Firebase Cloud Messaging, Push notifications in Android mobile app, and Android certificate set.

PEGA0107 alert enables performance monitoring of offline-enabled apps

You can now monitor the performance of offline-enabled apps by analyzing PEGA0107 alerts from Pega Predictive Diagnostic Cloud™. PEGA0107 alerts are equivalent to PEGA0069 alerts in the context of offline-enabled applications, but PEGA0069 alerts are not generated for offline-enabled applications.

For more information, see PEGA0107 alert: Client page load time for offline-enabled applications and Pega Predictive Diagnostic Cloud Improvement Plan overview.

Mashup code preview in App Studio

When you create a mashup channel for your application, you can now eliminate issues with the code and create better looking applications, by using the portal preview in App Studio. You can preview a channel to verify that different types of devices correctly display the mashup code. The preview functionality uses a default wrapper that functions as a portal for displaying a frame with the mashup code. You can modify the appearance of the default wrapper, and adapt the mashup user interface in design mode to meet your requirements.

For more information, see Configuring the Mashup channel and Previewing an application.

Default support for the OAuth 2.0 framework in custom mobile apps

You can now build custom mobile apps by using Pega Infinity Mobile Client or Pega Mobile Client 7 with the OAuth 2.0 authorization code grant flow that is enabled by default. This industry-standard authorization framework increases the security of custom mobile apps. Set up your application to either redirect to a login screen of a specific identity provider, or display a selection of available identity providers upon login. Settings for authentication services are now applied automatically when you build your app. You can ensure that a custom mobile app is secure by using a protection schema, such as a biometric sensor or a custom pin.

For more information, see Build secure custom mobile apps with the OAuth 2.0 framework.

Mobile channel enhancements

The Mobile channel now supports several enhancements to Pega Infinity Mobile Client™ and provides custom mobile app options that are arranged in a more intuitive, consistent, and convenient layout. By default, custom mobile apps that you configure within the Mobile channel are generated with Pega Infinity Mobile Client. You can choose between a single webview web portal or a multi webview application layout, and configure such options as: bottom bar navigation rule, the bottom bar style, and the full screen search widget. You can also build a custom mobile app with Pega Mobile Client 7, or select a specific version of the client application.

For more information, see Configuring a custom mobile app.