Identity Broker v4.0 feature requests

What I feel is missing with IdB is the ability to control it via Event Broker. With the improvements to EvB's scheduling, it would be great to be able to use it to run synchronisations in IdB.

We saw your request for this during the development of EB v3.0 and we love the idea. Unfortunately Identity Broker wasn't exposing enough for us to be able to do this - although we could have triggered operations, we couldn't have monitored their status or been notified of when they were complete.

For Identity Broker v4 we will be exposing this to external applications, including Event Broker, and for v3.1 will include new Identity Broker operations to control things such as imports.

It would be a great thing to export IdB config into a human readable format, or have a parser that can process an export file for inclusion into documentation in a similar fashion to the MIIS documentation toolset in the MIIS resource kit.

Part of this will be solved with the introduction of a sensible UI that can show you all this information in a central location, but we'll certainly look at providing some level of this in a report. See IDB-129.

Also, please, please, please that XML image node must go!

Already done!

Thank you again for the requests.

Thanks Patrick - can't wait for IdB 4.0!

Mark - I have created XSLT documents to transform both Event Broker 3.* and Identity Broker 3.* extensibility files. Let me know if you want a copy of them - they are designed to be used with the FIM Object Visualizer tool (same HTML styles).

Mark (and anyone else wishing to generate documentation for Event Broker and Identity Broker versions 3.*) ... please download https://unifysolutions.jira.com/secure/attachment/12652/FIM+Object+Visualizer.zip and speak to me about how to use it. This is in advance of formal documentation generation built into the products.