Adventures in identity management
MiisApp was designed to be a toolset for non-administrative users who needed to interact with MIIS in certain, well-specified ways. Some of these tasks do not directly involve MIIS itself, but are for setting up the data appropriately – such as the forms for viewing source data. An issue that came up from time to…
To try and decrease my code maintenance on MiisApp I introduced a number of dynamic menus that were built at application startup, and then refreshed periodically. Now I don’t want to go into all the code specifics here. I am not a software developer, and the code I wrote for this application was very site-specific. However…
A big priority in cobbling together a client application for MIIS was to provide evidence that MIIS was in business. If people could watch MIIS in action they would, by degrees, start to feel more comfortable with it – in what order it did things; how long a typical cycle takes; and just general warm-fuzzies…
I think it’s fair to say that the majority of problems encountered in an IdM installation are to do with data. Data that’s wrong, data that’s missing, data that includes illegal characters or 17 tabs at the end – the possibilities for bad data really are endless. One of the messages I found myself attempting…
One of my complaints about MIIS has always been the lack of a client application that can be run on a workstation. In any organisation large enough to need (and afford) MIIS there are going to be multiple people who need to interact with it. They may not be scheduling syncs, but they could well…