FIM CM: How to start a renew workflow programmatically?
Hello all, is it possible to programmatically submit and execute a renew request via any of FIM CM's documented APIs? From what I understood, neither is possible using the Provision API and only request submission is possible using FIM CM SQL API. My further questions are: Am I correct in my understanding of FIM's APIs? Are there any official APIs I am missing here? Is there any kludge/workaround that would allow me to programmatically execute the renew workflow? Thanks in advance and best regards Nils Loeber
December 16th, 2010 12:49pm

Not sure how you plan to submit and execute a renew request. Can you please provide your desired workflow? Typically, you would have the FIM CM Update service initiate the Renew workflow with its service account. The subscriber would then execute the workflow. The workflow would be transferred by sending an OTS to the subscriber. The renewal request would be initiated by the FIM CM Update service when it detects that the profile has entered its renewal period. Brian
Free Windows Admin Tool Kit Click here and download it now
December 16th, 2010 4:12pm

Brian, thanks for taking the time to answer! My desired workflow is as follows: An external system will generate a notification of the soon-to-expire certificate; acting upon this notification, Person A must be able to request the renewal using a custom GUI, while Person B must be able to use the same custom GUI to approve the request. The certificate holder will then retrieve the certificate via the regular FIM CM self service GUI. I just had a revelation: I probably don't need to execute the renew request programmatically, do I? I could initiate the request using the external API (a little inconvenient, but feasible), use the RequestOperations.Approve method to approve the request and then the certificate holder himself would execute the request using the regular FIM CM GUI. Is that correct? Best regards Nils
December 17th, 2010 4:35am

Nils, Your approach should work. At a high-level, I would see it working in the following fashion: Person A would use the custom GUI to request the renewal; The application would initiate a renewal request into FIM CM using the External SQL API; The FIM CM Online Update Service processes the pending external requests, creating a proper Renew request in FIM CM; At this point, I would use the Notification API to capture the fact that the Renew request has been created and advise (by e-mail?) Person B of a pending request requiring approval; Using the custom GUI, Person B would retrieve and approve the Request details using the Provisioning API; I would configure email notification and OTP in the Renew policy to email Person A and advise them that their Renew request has been approved and what steps to follow to complete the renewal. Cheers, Marc Marc Mac Donell, ILM MVP, VP Identity and Access Solutions, Avaleris Inc.
Free Windows Admin Tool Kit Click here and download it now
December 17th, 2010 1:36pm

Hello Marc, Thank you, I'll try it that way then. Best regards Nils Loeber
December 20th, 2010 12:26pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics