Looking for a Clear Configuration Documentation Tool for SailPoint IdentityIQ (Similar to MIM Documenter)

IdentityIQ (IIQ) IIQ Discussion and Questions
, ,
1

Hello everyone,

I’m currently working on a SailPoint IdentityIQ environment and I’m trying to create clear and comprehensive documentation for the system configuration.

In Microsoft Identity Manager, there is a tool called MIM Configuration Documenter which generates well-structured and easy-to-read documentation for the entire environment (policies, workflows, schema, sync rules, etc.).

In SailPoint, I am currently using the IdentityIQ Object Exporter Plugin, which helps in exporting configuration objects (XML). However:

  • The output is not well-structured for documentation purposes

  • It is difficult to read and analyze

  • It doesn’t provide a clear, consolidated view of the environment

What I’m really looking for is something that:

  • Provides clear and human-readable documentation

  • Covers key components (applications, rules, workflows, roles, policies, etc.)

  • Helps with audit, troubleshooting, and knowledge transfer

:red_question_mark: Questions:

  1. Is there any tool (official or community-based) that provides clear documentation similar to MIM Documenter?

  2. How are you documenting your IdentityIQ environments in a structured and readable way?

  3. Has anyone built a custom solution (e.g., transforming XML exports, using APIs, or reporting tools)?

If no such tool exists, I’m also considering building a custom solution, so any guidance or shared experience would be highly appreciated.

Thanks in advance!

2

@IslamElkhouly Check if this article helps you out: https://community.sailpoint.com/t5/Technical-White-Papers/IdentityIQ-Technical-White-Papers/ta-p/169455

It contains lot of whitepapers for different modules. Each module should have their own doc containing the configuration details. Also, Sailpoint provides USer and Admin guides.

Regarding the artefacts available in the environment, we also used Export Object task and also prepare a Technical Doc containing the details about the module we currently working on. there is no such configuration documenter available in IIQ.

3

no, there is no true “MIM Documenter equivalent” for SailPoint IdentityIQ out of the box—and you’re running into a very common pain point.

Most teams end up stitching together their own solution. I’ll break this down cleanly so you can decide what direction actually makes sense.

1. Is there a native / official tool like MIM Documenter?

No.

SailPoint gives you:

  • Object Exporter (XML)

  • Debug pages / config browser

  • Limited reporting

But nothing that:

  • Normalizes relationships (apps → roles → policies)

  • Produces human-readable diagrams or docs

That’s by design—IIQ is highly customizable, so a generic documenter is hard to standardize.

2. What people actually do in the real world

Option A — Transform the XML (most common + realistic)

You already have the raw material. The trick is post-processing it.

Typical approach:

  • Export XML via Object Exporter

  • Parse with:

    • PowerShell

    • Python (lxml / ElementTree)

  • Transform into:

    • Markdown / HTML docs

    • Excel (for auditors)

    • JSON (for visualization tools)

What people build:

  • App inventory (connectors, schemas, rules tied to them)

  • Role model mapping (IT roles, business roles, entitlements)

  • Workflow summaries

  • Policy + rule references

Why this works:

  • You control structure

  • You can normalize relationships (which IIQ doesn’t do natively)

Option B — Use the IIQ API (cleaner than XML)

Instead of XML dumps:

  • Query objects via API or Beanshell tasks

  • Pull structured data:

    • Applications

    • Identity attributes

    • Roles

    • Certifications

    • Workflows

Then:

  • Push into a reporting layer (Power BI, ELK, etc.)

This gives you:

  • Cleaner data model than XML

  • Easier joins across objects

Option C — Build a documentation pipeline (best long-term)

This is what mature teams do:

Pipeline example:

  1. Extract (XML or API)

  2. Normalize (script)

  3. Store (JSON / DB)

  4. Render:

    • Confluence pages

    • HTML site

    • Diagrams (Graphviz, Mermaid)

Output:

  • “Living documentation”

  • Always up to date (huge for audits)

4

In older versions of the SSB (i.e 6.1) they had an Ant target which would generate docs from your XML config objects. Perhaps you could resurrect it. They deprecated it in newer versions.

image
image1404×778 246 KB

5

I believe none of these solutions are what OP asked for. The XML Exporter just creates an importable XML. The javadoc code is still available on Compass but it’s for java not for XML. What OP is asking for is a way to generate some kind of readable documentation based on what’s in the XML.

I have been working on my Documenter plugin for about 5 years, in my spare time, which is not much since I mostly spend my time on billable tasks. I do have some functionality, such as the ability to export an MS Excel spreadsheet of the ObjectConfig-Identity object. I wrote some tasks for role documentation and started a task to write an MS Word design document for an Application object. It’s not something you can boil down easily. Custom solution probably is what you want.