0
Answered

Force connector delta import to run after export

Carol Wapshere 8 years ago in PowerShell connector updated by anonymous 8 years ago 4

I want the delta import to run immediately after the export without having to schedule it to run on its own. Is there a way I can trigger the delta import from the end of the Export script?


I did see something on the Google Apps Connector topic about import-after-export but can't see any such setting in the IdB 5 UI.

Answer

Answer
Answered

This is possible using the REST endpoint. Use the same operation that EB uses to trigger an import. Unfortunately Confluence is down at the moment so I can't link it.


This feature is on the Google Apps connector for quite a specific reason - as the v4.1 connector can export without waiting for the result, the import needs to run afterwards. It's not in v5.0 as batched exports make it unnecessary.


Let me know your use case if you would like a more generic feature to be added to Identity Broker.

Answer
Answered

This is possible using the REST endpoint. Use the same operation that EB uses to trigger an import. Unfortunately Confluence is down at the moment so I can't link it.


This feature is on the Google Apps connector for quite a specific reason - as the v4.1 connector can export without waiting for the result, the import needs to run afterwards. It's not in v5.0 as batched exports make it unnecessary.


Let me know your use case if you would like a more generic feature to be added to Identity Broker.

+1

Thanks Adam - can you come back with the link when Confluence is back? Thanks.


As a general rule I like to be able to do a confirming import following an export.

The EB operation is here. Identity Broker documentation is internal at the moment on IDB-873, but will be expanded on as we add more functionality (road-mapped).

This looks to work:


$URI = "http://localhost:59991/IdentityBroker/api/1.0/Connector/PollChanges/212e8bdf-3ce1-450b-b9ef-71cb90149b55"

invoke-restmethod -uri $URI -Method Post