-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Kevin Wigle wrote: > Currently, we have an admin (me) create a blank map and then grant > permissions to it for the group requesting. > > We would like the ability to grant a group permission to also create maps > who are not "administrators" as admins have control over all maps (and the > entire server). Create a map but not have server admin rights. > > One of the objectives is to have different groups "share" Intermapper so > that network monitoring/scanning/reporting are centred in one managed > application. Having the ability the create their own maps, groups would not > need to ask the central admin to make one for them.
This is another situation that virtually mirrors our own, both in terms of how we currently handle it, as well as our wish list for future features. What I would like to add to this is the possibility of making maps hierarchical, where one could assign a certain subset of maps as being children of a parent map. The way I would use this would be to have the children represented on the parent map as "Map Status" probes. Where this fits into the graduated administrative control discussion is that it'd be nice to be able to dole out map-creation permissions on a similar hierarchical basis. For instance, I could assign a user "admin status" on a particular parent map, which would allow him or her to then create child maps of that parent, but not to create other parents. This would naturally aid in cleaning up/uncluttering the map list in Intermapper Remote, as well: maps could be listed in a more tree-type view, to be expanded and contracted by the user as desired. > In the administrative area, it would also be great if Intermapper could use > a different user database such as Active Directory. Our network community > is trying to discourage separate user databases with the ever present idea > of single sign on. I would like to second this request as well. We find Intermapper user management to be burdensome and tedious, as well as difficult to keep in sync with other access lists throughout our organization. Thanks, Mike Chesnut CITES Systems Management Group University of Illinois -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFfq/3guKIyhCbze0RAjLXAKC3zos/lY9OYuMzRGUvm7m5EE2y6ACg0DHn 8KmPbOwoPduKVY9girFBGXo= =/6qG -----END PGP SIGNATURE----- ____________________________________________________________________ List archives: http://www.mail-archive.com/intermapper-talk%40list.dartware.com/ To unsubscribe: send email to: [EMAIL PROTECTED]
