Changelog

The following is the change history for the PingOne Integration Kit. Updated May 30, 2024.

PingOne Integration Kit 2.7 - September 2024

Fixed an issue that could cause a delay in retrieving an updated user schema.
Added the ability to skip retrieving user group and device details during datastore lookup.

Added the ability to exclude retrieving user group, device details, and password expiration information during password credential validation.

Fixed an issue that caused values retrieved from the PingOne datastore for custom multi-value attributes to be formatted incorrectly.
Fixed an issue that caused disabled user accounts to receive an account recovery email if the account recovery flow was triggered.

Fixed an issue that caused an error when trying update the population ID attribute.

Added support for group provisioning.
Added the ability to select which device will be the default device on user creation.
Added the ability to select voice as an option for offline device pairing.
Fixed an issue that prevented all of a user’s authentication methods from being provisioned if any of them were invalid.
Fixed an issue that allowed duplicate local attributes to be defined when configuring an adapter.
Fixed an issue that could cause an attribute containing an array of objects to be returned in the incorrect format.
Fixed an issue that caused password validation to fail intermittently when the user’s access token expires.

Added support for custom string attributes for provisioning to the PingOne Datastore.
Fixed an error that prevented a user with an expired password from changing their password.

Added the provisioning connection status to the PingOne connection summary page.
Fixed an issue that, after upgrading the PingOne Datastore component, caused an error when using the administrative API to bulk import an earlier version of the PingOne Datastore.

Fixed an issue that could cause an error in the sign-on flow when the user entered an invalid password.

Added support for the PingOne platform connection that was introduced in PingFederate 10.2.
Added support for the identifier first action in PingOne. You can now map an Authoritative IdP value when configuring the provisioning channel.
Added the ability to select PingOne populations from a pre-populated list when configuring the provisioning channel.
Added support for authentication method nicknames. The provisioning connector can now use nicknames to identify and update authentication methods.
Added the ability to get a user’s group membership information from PingOne.
Improved the error message that appears when a user tries to change their password too frequently.
Improved validation rules and error messages for some configuration fields.

Added a PingOne region list to provisioning options. This allows the provisioning engine to target the PingOne API in your region.

Changed name to PingOne Integration Kit in support of new and future PingOne services.
Added support for managing users' SMS and email devices for PingOne MFA.
Improved logging abilities.

Fixed an issue that caused the adapter to fail when a key-value attribute was mapped with JSON Pointer syntax.
Improved the input validation for the Custom Proxy Host field in the password credential validator configuration.
Improved the error message that a user sees when they try to change their password too frequently.

Added the ability to override the system-default proxy settings in the data store configuration.
Added the ability to customize authentication error messages in the password credential validator configuration.
Improved the error messages that appear when a user tries to set a password that doesn’t meet the password policy.
Fixed an issue that prevented users with empty attributes from being provisioned to PingOne.
Removed support for obsolete scopes from the provisioning connector and data store configuration screen.

Added the ability to use PingOne as a data store and password credential validator.