December 2023

New PingOne Mobile SDK

Version 1.11 of the PingOne MFA mobile SDK for Android has been released.

This version contains a number of bug fixes.

See Release notes - Android version.

Improved PingOne Mobile SDK

The sample app for the PingOne MFA mobile SDK has been updated to demonstrate support of passkeys. This applies to both the Android and iOS versions of the sample app.

Improved PingOne Authorize

Now you can extend Kong’s authorization capabilities with an integration kit that supports Kong Konnect. This integration allows you to centrally manage your authorization requirements using PingOne Authorize’s external policy evaluation service, controlling access to APIs with simple rules and fine-grained policies. For more information, see Integrating PingOne Authorize with Kong Konnect.

Improved PingOne Authorize

We’ve made it easier to add runtime authorization controls to your existing PingOne configuration. In PingOne, a resource represents your API for OAuth authorization purposes. Now you can assign existing PingOne resources to API services, adding runtime API Access Management controls around your previously modeled APIs. For more information, see Defining your API in PingOne Authorize.

New PingOne

You can now filter groups by external source, such as an external identity provider or LDAP Gateway, and by population. For more information, see Searching for groups.

New PingOne

To simplify user configuration after you add a large number of users to PingOne, you can now set a default identity provider for a population. This setting applies to any users in the population who do not have Authoritative Identity Provider defined in the their user profile, and applies only as long as the user remains in the population. This setting does not affect the Authoritative Identity Provider setting on the user profile. For more information, see Managing populations.

New PingOne Verify

PingOne Verify now supports inspection type for government ID. Inspection type determines the type of inspection performed on government-issued documents and offers automatic, manual, and step-up to manual options. For more information, see Creating a verify policy.

Improved PingOne

We’ve released LDAP Gateway client application version 3.0.4. This version improves performance, and requires Java 17.0.8 (or later) or Java 21 LTS (or later). For more information, see LDAP gateways.

New PingOne MFA

When you customize the template for the message that is sent to notify a user when a new device is paired for their account, you can now include a variable called report.fraud. If you include this variable, the message will include a link that the user can click to report fraudulent pairing attempts. PingOne records these reports and you can view them in the Audit log. The event type for these reports is Fraud Reported.

Info PingOne MFA

We’ve added a warning message to MFA policy to ensure administrators are aware that using the Ping sender account for SMS and Voice calls incurs charges. The popup message also appears when switching from a custom sender account to Ping’s sender account. To discourage the use of less secure authentication methods when creating a new MFA policy, the Voice authentication method is not selected by default.

New PingOne Verify

The PingOne Neo Verify User Data endpoint and its only call, Read User Verification Data, are deprecated. The endpoint and request will be removed December 2024. For more information, see User Data and GET Read User Verification Data.