PingOne Connector Release Notes

Improved

You can now use the Read Population capability to determine a user’s population based on an alternative identifier value and can also specify a theme to support multi-brand authentication experiences.

Improved

The following capabilities allow you to manage group metadata.

The following capabilities now update the p1userid global variable in DaVinci with the user ID when the user is successfully found:

This update allows you to use the p1userid global variable in the flow to ensure the user ID will be populated at the right times.

You can use the new Authenticate User Via Kerberos capability to authenticate Active Directory users seamlessly through the Kerberos protocol.

Previously, when searching for users with Find User and Find Multiple Users, the capability builds a SCIM filter based on a list of attributes and a search term.

You can now provide your own filter by toggling on the new Custom SCIM Filter field, allowing you to pick the operators used for filtering and allow different values to be searched for each attribute.

Improved

The Create User and Update User capabilities mappings no longer pass empty values to PingOne. Previously, PingOne sent an error to DaVinci due to empty values.

If a field is included with no value, the connector would normally pass it to PingOne as an empty string. If no field or value is included, the connector would normally pass it as a null value. Now, these values are omitted and not passed as empty values.

The following new capability allows you to unlock a locked PingOne user account:

New

To support group manipulation during flows in DaVinci, we have added the following capabilities:

These allow you to create, manage, and read groups in a PingOne environment.

You can now use the Find Multiple Users capability to search and return up to 100 users.

include::partial$common_product_keydefs.adoc[tags=pingone]users

The following new capabilities allow you to manage which groups a user belongs to:

Combined with the existing Read User Group Memberships capability, this provides you with a more complete membership management experience.

New

The new Migrate User through Gateway capability allows you to authenticate a user against an LDAP gateway set up in include::partial$common_product_keydefs.adoc[tags=pingone], then automatically migrate the account to the main include::partial$common_product_keydefs.adoc[tags=pingone]user store.

By integrating this into your existing authentication flow, you can migrate users gradually as they sign on.

The Gateway User Type List property allows you to filter by specific gateways and user types.

New

This change allows you to set a flag that forces a user to set a new password next time they sign on.

Previously, the new password had to be set by the administrator when flagging the account.

Improved

When configuring a connector capability, include::partial$common_product_keydefs.adoc[tags=singularkey]now populates properties, such as Population and Agreement, with information from include::partial$common_product_keydefs.adoc[tags=pingone].

Your existing configuration still works, and you can always select Use Population ID (or the equivalent) to show a manual entry field. This lets you manually enter a value or use a dynamic value from your flow.

Improved

Previously, the Create User and Update User capabilities allowed you to define additional user attribute mappings by manually typing attributes and values in the Other Attributes section.

To make the configuration more convenient, the attribute names and data types are now populated automatically from your include::partial$common_product_keydefs.adoc[tags=pingone]environment.

Improved

All connector capabilities now use the default error messages from the include::partial$common_product_keydefs.adoc[tags=pingone]API. This makes it easier to set up a flow with meaningful error messages.

You can override these messages on the Mappings (Error Messages) tab of the capability configuration.

Improved

When configuring capabilities that need a population, you can now select Use Default Population instead of selecting a specific population.

When you set a default population in include::partial$common_product_keydefs.adoc[tags=pingone], all capabilities with this setting will automatically use that population.

You can use the PingOne connector to: