-1
Completed

Alternative approach to dealing with export timeouts to IdB

Bob Bradley 2 years ago • updated by anonymous 1 year ago 2

An alternative to having to change batch size/timeout settings on export, it might be worth considering adopting a similar approach that Microsoft did with the MIM (Service) MA - i.e. changing the default option to asynchronous instead of synchronous exports.

Under the current default configuration, the MIM MA gets a success returned from the MIM Service once an exported change has been successfully queued (inserted in the REQUEST - either single or batch request objects). A similar approach might be worth considering for IdB such that we can decouple long-running connector export times from the MIM export itself.

I am categorising this request under O365 because that is where I am seeing the most need for this feature right now - however this would be a generic option.

Affected Versions:
Fixed by Version:

Answer

Answer
Completed

Will be investigated as part of a roadmapped item on more granular and expanded set of export results - that could possibly include an export status of async/pending.

Under review

My concern with this issue is that it breaks the contract that MIM has with Identity Broker, namely that we provide the result of the operation back to FIM synchronously.

Answer
Completed

Will be investigated as part of a roadmapped item on more granular and expanded set of export results - that could possibly include an export status of async/pending.