So what about connecting FIM CM to FIM Synchronization and FIM Service?
If you look at your FIM Synchronization Service, you will find that you can create a Management Agent for Certificate Management. This MA is used to connect to FIM CM.
This MA is not used very often, since it is basically not that good. In FIM CM, the ID used for users is AD GUID
. So in order for us to join our users with the objects in FIM CM, we need the objectGUID attribute from AD in our MV. And for some unknown reason the MA is preconfigured to Join using guid
.
The usage of this MA, as I have said, is limited. If you initiate a request using this MA, the request would end up as pending in the FIM CM portal and the user would still be required to go to the FIM CM portal to finalize the request.
I have also used this MA to import the status from FIM CM into FIM, in order to gather the current status of FIM CM requests into FIM, and then use the FIM Service to act in case the request or profile show...