June 30
PingOne Risk is now PingOne Protect
With Bot Detection and Suspicious Device predictors, PingOne Protect enhances detection and helps prevent account takeover and new account fraud. For more information, read the PingOne Protect datasheet.
If you are a current PingOne Risk customer, this change doesn't affect your service. To learn more about the new capabilities, reach out to your account team.
Encryption key rotation
June 29
PingOne MFA mobile SDK 1.10
Version 1.10 of the PingOne MFA mobile SDK has been released.
This version includes encryption key rotation once a year.
See Release notes - Android version and Release notes - iOS version.
Encryption key rotation
June 28
User license limit warnings
June 26
Run the LDAP Gateway as a Windows service
You can now run the PingOne LDAP gateway as a standalone service on Microsoft Windows. You’ll do this by downloading a ZIP archive and adding the service to a computer running Windows. This feature is in addition to the existing options of running the PingOne LDAP Gateway as a Java application or in a Docker container. For more information, see LDAP Gateways.
June 22
Request Parameter Signature Requirement
June 20
New authorization comparators for IP subnet ranges
FIDO authentication methods and FIDO policy enhancements
To enhance the FIDO2 authentication experience, we are expanding FIDO policies to include a broader set of configurations that provide you with more granular control over your FIDO2 authentication devices. For best practice guidance, we're also providing two out-of-the-box FIDO policies, pre-configured to allow Passkey and Security Key authentication.
To facilitate this change we are deprecating the existing FIDO Biometrics and Security Key authentication methods in the MFA Policies, and replacing them with a single, comprehensive FIDO2 authentication method. For information about adding the enhanced FIDO policy, and the new features it provides, see Adding a FIDO policy.
If you have an MFA policy that references a deprecated authentication method, we recommend that you replace it with the FIDO2 authentication method, and reference an enhanced FIDO policy. You will also need to update any related scripts and DaVinci flows that reference the deprecated authentication methods. For information, see Updating an existing MFA policy to use FIDO2.
FIDO authentication methods and FIDO policy enhancements
June 12
Push settings for Google Play-based apps
PingOne MFA has moved to Firebase Cloud Messaging for sending push messages.
This impacts the credentials you must enter when enabling push notifications for Google Play-based mobile applications.
For details, see Editing an application - Native and the Application MFA Push Credentials section in the API documentation.