June 2024 - PingOne - PingOne Cloud Platform

PingOne Cloud Platform

bundle
pingone
ft:publication_title
PingOne Cloud Platform
Product_Version_ce
PingOne
PingOne Cloud Platform
category
Administratorguide
ContentType
Guide
Product
Productdocumentation
p1
p1cloudplatform
ContentType_ce
Product documentation
Guide
Guide > Administrator Guide

June 28

Verify policy enable AAMVA

PingOne Verify
New
We’ve added a new feature for Verify policies, Enable AAMVA. This allows verification of ID information against the issuing agency database. Learn more in Creating a Verify Policy.

June 26

Delegated administration for applications

PingOne
New
We’ve created the Application Owner role to limit administrator access to specific applications. Use this role to provide application developers with access only to the applications they manage. This role provides no other administrator permissions in PingOne. Learn more in Administrator Roles and Managing user roles.

User interface updates

PingOne
Improved
To ensure consistent terminology throughout the product, two user interface (UI) updates have been made:
  • In the sidebar, under Directory, Roles is now Administrator Roles.
  • In the Users UI, the Roles > Administrative Roles tab is now Roles > Administrator Roles.

Learn more in Administrator Roles and Managing user roles.

June 25

Verify policy fail expired IDs

PingOne Verify
New
We’ve added a new feature for Verify policies, Fail expired IDs. This allows users to fail verification when an ID expires. Learn more in Creating a Verify Policy.

June 20

Updated LDAP Gateway client application

PingOne
New
We’ve released LDAP Gateway client application version 3.1.2. This version includes:
  • Docker image support for ARM-based hardware and virtual environments, providing more flexibility on how you run your LDAP gateway. Docker automatically pulls the right image, so no action is required.
  • Bug fixes for external password policy enforcement
  • Logging enhancements

Learn more in LDAP Gateways and the new Best practices for configuring Active Directory for LDAP gateways.

June 18

Specifying flow subtype for risk evaluations

PingOne Protect
New
When creating risk evaluations, you can now provide additional detail about the context of the flow by specifying a flow subtype in addition to the flow type. For details, see the description of the new flow.subtype field in the PingOne API documentation.

June 17

Providing feedback for risk evaluations

PingOne Protect
New
A new endpoint, riskFeedback, has been added to the PingOne API to allow you to provide feedback on the accuracy of specific risk evaluations that were carried out. Each such call can include feedback for up to 100 risk evaluations, and for each evaluation you can specify a feedback category and a reason for including the evaluation in that category. For details, see Providing feedback for risk evaluations in the API documentation.

June 14

Population overview

PingOne
Improved
We’ve updated the Populations UI into corresponding sections to easily help navigate through various configurations. Admins can now see details attached to a population within the populations UI, along with the ability to navigate to corresponding configurations in Password Policy and External IdP when needed. Learn more in Managing populations.

June 11

CORS support extended

PingOne
Improved
We've extended support for cross-origin resource sharing (CORS) to additional endpoints in PingOne. CORS allows devices on one domain to access resources on another domain. Learn more in Cross-origin resource sharing and in the Cross-origin resource sharing section of the PingOne API documentation.

June 4

Dynamic linking for FIDO transactions

PingOne MFA
New
For MFA, the PingOne API now includes an option to use dynamic linking to attach a unique identifier to a FIDO transaction. For details, see Create a request property JWT and Device authentications data model in the PingOne API documentation.

June 3

Allow user to add device nickname during pairing

PingOne MFA
Improved
We’ve added the option to allow the user to add a device nickname during the pairing flow. After successfully pairing the device, a popup window is shown, asking them if they want to define a device nickname. If the user does not edit the text field, the default nickname is applied.

For more information, see Adding an MFA policy.