Our use case is as follows:

• we have a SAML related OIS plugin which creates an OrgIdentity during enrollment
• we want this SAML data to be authorative over all user data; any data the user enters should be next to and not instead of this data
• this data needs to be synchronised with the SAML data as much as possible

OIS allows synchronising the SAML data on login with the OrgIdentity.

Pipelines allow synchronising the CoPerson data with OrgIdentities.

However, currently, although pipelines are supported for OIS, the created CoPerson record is not correctly associated in the enrollment.