IID's History Plugin, particularly in combination with our other plugins, remains the state-of-the-art for IIQ Identity History. It does not compete with IIQ's new Access History, but rather the two complement one another.
View detailsThis quick post will be about various wrappers in the Utilities and Metered classes. These classes provides lambda-based API for fluently decorating your SailPoint IIQ code.
View detailsIIQCommon's table class provides a fluent, type-safe API for generating HTML tables in IIQ scripts.
View detailsThingAccessUtils implements the Common Security behavior behind most of Instrumental ID's plugins, utilities, and other IIQ enhancements
View detailsThis will be part of a blog series providing an overview of the many SailPoint IIQ utilities and tools available in Instrumental ID’s open-source iiq-common-public library. (For an overview of the entire library, see this earlier post.) This post will be about the “Hybrid Object Matcher” utility. This utility expands on the matching tools available…
View detailsThis will be part of a blog series providing an overview of the many SailPoint IIQ utilities and tools available in Instrumental ID’s open-source iiq-common-public library. (For an overview of the entire library, see this earlier post.) This post will be about the BaseCommonPluginResource, the superclass to nearly all of Instrumental Identity’s web services. This…
View detailsRewriting URLs The problem Let’s say you’ve written a custom SailPoint IdentityIQ (IIQ) plugin that exposes a plugin page. By default, plugins in IIQ have a technical-looking URL, like this: https://iiqdemo.example.com/identityiq/plugins/pluginPage.jsf?pn=PluginName. That’s both too much and too little information for an end user. If your page consumes Angular state, it might have an even uglier…
View details