Switching connector with a different reconciliation attribute

Resolved

We currently manage a population of identities entirely through a connector (for example, a CSV import), including their creation and lifecycle management.

We now want to switch to a new connector (also CSV-based) to manage the same scope of identities. In this new connector, the reconciliation (correlation) attribute will be different from the one used previously.

What is the recommended approach to transition from the old connector to the new one while ensuring that:

  • existing identities are correctly linked to the new connector using the new reconciliation attribute,

  • no duplicate identities are created,

  • and lifecycle management (creation, updates, deactivation/end of lifecycle) continues seamlessly under the new connector?

Thank you in advance for your help.

Import, export & provisioning
1 reply