---
title: October 2022
description: New PingOne Connector
component: connectors
page_id: connectors::relnotes/archive/2022-10-October
canonical_url: https://docs.pingidentity.com/connectors/relnotes/archive/2022-10-October.html
llms_txt: https://docs.pingidentity.com/connectors/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
revdate: January 16, 2026
section_ids:
  october-10: October 10
  manage-group-memberships-for-pingone-users: Manage group memberships for PingOne users
  migrate-users-from-an-ldap-datastore-to-pingone: Migrate users from an LDAP datastore to PingOne
  force-a-user-to-set-a-new-password-next-time-they-sign-on: Force a user to set a new password next time they sign on
  dynamically-populated-capability-fields: Dynamically populated capability fields
  simpler-attributes-list-for-creating-and-updating-users: Simpler attributes list for creating and updating users
  default-error-messages-for-capabilities: Default error messages for capabilities
  use-your-default-pingone-population: Use your default PingOne population
  get-transaction-status-now-outputs-the-complete-transaction-status-details: Get Transaction Status now outputs the complete transaction status details
---

# October 2022

## October 10

### Manage group memberships for PingOne users

New PingOne Connector

The following new [PingOne Connector](../../p1_connector.html) capabilities allow you to manage which groups a user belongs to:

* **Create User Group Membership**

* **Delete User Group Membership**

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

### Migrate users from an LDAP datastore to PingOne

New PingOne Connector

The new [PingOne Connector](../../p1_connector.html) **Migrate User through Gateway** capability allows you to authenticate a user against an LDAP gateway set up in PingOne, then automatically migrate the account to the main 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.

### Force a user to set a new password next time they sign on

New PingOne Connector

In the [PingOne Connector](../../p1_connector.html), you can now 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.

### Dynamically populated capability fields

Improved PingOne Connector

![A screen capture of the user configuring the Population ID field.](../../_images/connector-images/dvc-p1-relnotes-population-id-configuration.gif)

When configuring a [PingOne Connector](../../p1_connector.html) capability, DaVinci now populates properties, such as **Population** and **Agreement**, with information from 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.

### Simpler attributes list for creating and updating users

Improved PingOne Connector

Previously, the [PingOne Connector](../../p1_connector.html) **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 PingOne environment.

### Default error messages for capabilities

Improved PingOne Connector

All [PingOne Connector](../../p1_connector.html) capabilities now use the default error messages from the 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.

### Use your default PingOne population

Improved PingOne Connector

When configuring [PingOne Connector](../../p1_connector.html) 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 PingOne, all capabilities with this setting will automatically use that population.

### Get Transaction Status now outputs the complete transaction status details

Fixed Challenge Connector

Previously, the [Challenge Connector](../../challenge_connector.html) **Get Transaction Status** capability would output a blank `details` object. It is now populated with the **Additional Fields** configured in the **Challenge** node that set the transaction status.