...
If more than one candidate CO Person is found, an error is thrown.
Note |
---|
Pipeline Match Strategies are unrelated to Enrollment Flow Identity Matching. |
Sync Strategies
Sync Strategies are used to determine when a CO Person record should be created or updated by a Pipeline, and whether an associated CO Person Role record should also be created/updated.
- Sync on Add/Update/Delete: These setting control when an Organizational Identity is processed using a Pipeline.
- Create CO Person Role Record: If checked, when the Pipeline executes it will create a CO Person Role record, not just a CO Person record. This is useful to (eg) automatically add someone to a COU based on their Organizational Identity Source.
- Sync to COU: If Create CO Person Role Record is set, this setting defines which COU the new Role Record will be placed into.
- Replace Record in COU: Not currently implemented.
- Role Status on Delete: If Create CO Person Role Record is set and the Organizational Identity Source record is deleted (no longer valid), the corresponding CO Person Role will be set to the specified status.
When a Sync Strategy executes, it copies all data provided by the Organizational Identity Source and any defined Group Mappings.
Connecting Pipelines
Pipelines can be connected to various contexts:
- Enrollment Flows
- Organizational Identity
...
- Sources
- To the CO itself (for Default Registry Enrollment)
This is also the order of preference. That is, if an Organizational Identity is created from an Enrollment Flow, and that Enrollment Flow also queries an Organizational Identity Source, and both the Enrollment Flow and Organizational Identity Source are connected to Pipelines, the Organizational Identity will be processed via the Pipeline connected to the Enrollment Flow.
Except when connected to an Enrollment Flow, when a Pipeline creates a new CO Person record, Identifier Assignment is triggered, and when a Pipeline creates or updates a CO Person or CO Person Role record, provisioning is triggered.
Pipelines are executed according to the current configuration, so it is possible for an Organizational Identity to be processed by a different Pipeline than the one it was originally attached to.
Enrollment Flows
Organizational Identity Source Sync
Default Enrollment
Manually Rerunning a Pipeline
...