I’m currently working with the IdentityNow (ISC) Search API to fetch certification-related events (create, sign-off) as part of a use case I’m testing.
While reviewing the response, I can see fields like the target name, but I don’t see the certification ID being returned. Since the target name may not be unique across certifications, this makes it difficult to reliably identify which certification the event belongs to.
Had a few questions on this:
Is there a reason why the certification ID is not included in the Search API response?
Is there any way (query, config, or expansion) to include the certification ID in the results?
I have a requirement to programmatically automate post-certification tasks for reviewers once certifications reach a signed-off state. This is intended to be implemented as an automated job that periodically scans for certifications that have been signed off.
However, I am encountering a limitation in identifying the final decision-maker (i.e., the user who performed the sign-off action), as this information does not appear to be readily available via search APIs along with the certification ID.
Additionally, I would prefer not to rely on the API approach that was mentioned, as it would require repeated querying and may not scale efficiently with the increasing number of certification campaigns over time.
I have explored the possibility of leveraging event trigger mechanisms to capture this information; however, I would prefer to avoid that approach unless absolutely necessary. My goal is to determine whether there is any configuration-based solution or API enhancement that would allow retrieval of both the certification ID and the sign-off user directly within the search API response.
Got it. Just to add—since the number of campaigns is increasing, you can filter them based on the modified date and where completed = true, as shown in the screenshot.
That said, this is only a suggestion. Since you mentioned you don’t want to proceed with the API approach, I’m currently out of ideas for the direction you prefer.
Can we know what those post-certification tasks are? Is it like sending email to cert reviewer (who signed off the cert)? If yes, we have done this using workflow. For this we have used “Certification signed off“ trigger where you will have all the info that you need.
using event triggers in SailPoint IdentityNow (ISC) does seem like a clean approach for invoking business logic on events such as sign-off.
However, I have a concern regarding the “fire-and-forget” nature of these triggers. In my use case, I need to execute some custom business logic when the event is triggered. If an error occurs during that execution (for example, due to a transient issue or downstream dependency failure), there doesn’t appear to be any mechanism within ISC to re-trigger or replay the same event.
This creates a potential reliability gap, since a failed execution could leave the process in an inconsistent state with no straightforward way to recover from the ISC side.
I have implemented a custom scheduled job that handles the sign-off event and performs the required post-processing for my business logic. However, I am encountering an issue when using the Search API to retrieve the event details.
The response currently does not include the Certification ID, which is critical for my use case. While the response does contain the certification name, this is not a reliable identifier since multiple certifications can share the same name.
And even if I use list certification campaign API, it would require iterating through all certification campaigns, performing additional filtering and lookups to identify the relevant certification, which introduces unnecessary complexity and processing overhead?
Given that the Search API is intended to provide streamlined access to event-related information, I would expect it to include a unique identifier such as the Certification ID to enable precise correlation.
Has anyone encountered a similar limitation with the Search API, or is there an alternative approach (other than event trigger)?
