March 2023 - 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 > Administrator Guide
Guide

March 31

Inbound user provisioning with SCIM 2.0

PingOne
New

PingOne now supports the SCIM 2.0 identity management standard for provisioning users into PingOne Directory. For more information, see SCIM in the PingOne Platform API Reference.

March 30

Default risk policy

PingOne Risk
Info

The default risk policy has been modified to provide better risk evaluation results out-of-the-box. The default policy now includes the New Device predictor, and the scores assigned to the predictors in the policy have been fine-tuned.

For details, see Risk policies.

Caching authorization service data

PingOne Authorize
New
Now you can cache service data that's frequently used. This reduces authorization decision latency and eases the load on external systems. For more information, see Authorization service caching.

March 27

New Device risk predictor - activation date

PingOne Risk
New

For New Device predictors, it is now possible to set an activation date to restart the learning process for the predictor.

This can be used in conjunction with the fallback setting to force strong authentication when moving the predictor to production.

March 26

Composite risk predictors - enhancements

PingOne Risk
Improved

In addition to combining existing predictors, you can now include the following risk factors in your composite predictors: country, state, IP range, IP domain organization, ISP, target resource (application).

For details, see Adding composite predictors and the Risk Predictors section of the API documentation.

March 24

Loopback IP redirect URIs

PingOne
New
PingOne now supports any valid port for loopback IP redirect URIs. Native applications that can open a port on the loopback network interface without needing special permissions can use the loopback interface to receive the OAuth redirect. This feature can help you lower administration costs by reducing the number of redirect URIs in your applications. For more information, see Redirect URIs.

March 20

PingOne Neo

PingOne Neo
New
PingOne Neo is a decentralized identity solution that gives control of identity data back to users and includes services such as PingOne Credentials, PingOne Verify, and PingOne Neo SDK.

For more information, see PingOne Neo documentation and the PingOne Neo website .

PingOne Credentials UX refresh

PingOne Credentials
New
To provide a better admin console experience, the following improvements have been made to the PingOne Credentials page. You can now:
  • Specify who a credential will be issued to or revoked from, Groups, Populations, and use the SCIM filter to further create conditions.
  • Choose Theme to customize a credential for your organization.
  • Select the Field Type that you want to collect: Directory attributes, Date of issuance or create Alphanumeric-text fields.
  • Assign a digital wallet for credential storage.

For more information, see Creating and managing credentials and Revoking credentials.

Getting Started with PingOne Credentials

PingOne Credentials
New
Developing and registering a wallet app that runs PingOne Neo SDK is now a part of getting started with PingOne Credentials. This can be done following the PingOne Neo SDK API document and in the PingOne Credentials admin console. For more information, see Getting Started with PingOne Credentials.

Enhanced Knowledge links

PingOne
Improved
The Help and Resources > Knowledge links now go directly to related documentation.

March 15

Changes to authenticating to the PingOne admin console

PingOne
New

As part of our ongoing effort to use current best practices and keep PingOne administrators and their environments secure, we’ve made some changes on how authentication is implemented in the PingOne admin console. In most cases, the changes should have no impact on your PingOne experience. For more information, see Editing an authentication policy.

March 13

Pairing key lifetime

PingOne MFA
New
When defining the settings for mobile applications in an MFA policy, it is now possible to specify how long an issued pairing key can be used until it expires. This can be set separately for each application.

Prevention of repeat push notification attacks

PingOne MFA
New
You can now define the number of consecutive push notifications that can be ignored or rejected by a user within a defined period before push notifications are blocked for the application. Use this setting to prevent attacks based on repeated push notifications that may lead users to eventually accept the authentication request. For details, see MFA policies and the API documentation for Device Authentication Policies.