Cool Solutions

the yin and yang of idm management


May 26, 2006 7:52 am






in my last post i asked you what console strategy you would prefer. i would now like to share some insights with you about what the designer for identity manager future holds. your posts have all been received and in my hallway where my office is i was called “trouble maker” for 2 weeks after my post.

see how designer for identity manager is going to address the issues that were brought up.

for the public, designer for identity manager started off as an offline only tool and we got overwhelmingly positive feedback to this new approach. now that designer for idm is in the maturing phase, we get a lot of requests for “live” features. you and others told us that it is awkward to alt+tab over to imanager, do an object modification, watch the trace to see the result and then alt+tab back to designer to make changes to the driver configuration, run the changes through the simulator, deploy them and again alt+tab back over to imanager.

we cannot comlete the whole visionary picture in a single milestone but we work one stroke of a brush after the other. some strokes have been painted long ago like the ability to start/stop/status drivers from designer and some are being painted at this very moment. in our next milestone release you will get access to another experimental live feature: an identity vault browser with object access.

Live Mode

the identity vault browser lets you browse every idv in your current project and allows to login to any other tree as well. the feature currently allows you also to edit any object with a generic object/attribute editor and you will be able to define customized ui for your schema on a per object class basis. in one of the future milestones we will add object creation, rename, move and delete.
imanager remains the primary edirectory administration tool for anything that goes beyond the above mentioned capabilties. designer and imanager are the yin and yang of idm management.

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.

Categories: Uncategorized


Disclaimer: This content is not supported by Micro Focus. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.


  1. By:James Tremblay

    it seems to me that Novell is allowing one department to reproduce work and features already shutdown\abondoned by another. In this case , ConsoleOne, I am not a fan of iManager at all it is slow and cumbersome to manipulate. there needs to be a unified management console with “snapins” for extended features. I say skip the rebuild and go add IDM services to ConsoleOne and bring all things adjustable back to this wonderful interface!

  2. a huge advantage of basing our tools on a community-driven framework like eclipse rather than developing and maintaining our own is that we can take profit from an already mature framework and a rich palette of community-contributed tools. our part is reduced to coming up with the functionality that is required to deal with our products (in this case identity management). on the other hand, whenever there are short comings in the framework, we fix them and contribute them back to the community. it’s a synergetic relationship.
    if you haven’t already done so, take a look at designer for identity manager and let me know what you think of it. i personally would never want to trade it with anything we ever had.