With the increase in social engineering attacks on the rise and the need for heightened security protocol and business processes around providing password and account support especially with the large amount of workforce being hybrid or remote, many organizations are finding it challenging to validate a persons identity. At Instrumental Identity we have worked with…
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.
This 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.
IIQCommon’s table class provides a fluent, type-safe API for generating HTML tables in IIQ scripts.
ThingAccessUtils implements the Common Security behavior behind most of Instrumental ID’s plugins, utilities, and other IIQ enhancements
This 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…
This 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…
Rewriting 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…
Continuing the discussion from In Sync & Secure: CI/CD Design Challenges and Considerations: Phase 1 of the DevOps solution standup process focuses on the many pre-deployment tests you can run to prevent issues from reaching your IdentityIQ environment and can leverage both SailPoint and custom tooling to meet your testing needs. Phase 1 also acts…
The minimum viable product of every DevOps solution is to reliably deploy an application in an automated fashion without any developer interaction (outside of optionally clicking a start button). Regardless of what pipeline platform you have available, your first consideration will be to follow a “push” or “pull” methodology for your pipeline. In the scenario…
