Inbound user provisioning with SCIM 2.0
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.
Default risk policy
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
New Device risk predictor - activation date
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.
Composite risk predictors - enhancements
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 Composite predictors and the Risk Predictors section of the API documentation.
Loopback IP redirect URIs
For more information, see PingOne Neo documentation and the PingOne Neo website .
PingOne Credentials UX refresh
- 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
Enhanced Knowledge links
Changes to authenticating to the PingOne admin console
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.